V G wrote:
> c h wrote:
>> A good PC at the development time, I think. Later you could analyze
>> the bottlenecks and choose the appropriate hardware configuration.
>
> This is by no means an uncommon application, file and webserver. I
> think the bottlenecks are already known to server
> administrators/whomever.
>
>> Posgresql should be placed on a separate hardware, I believe.
>
> The load on the database daemon will be relatively light. It is not a
> database intensive task - but I'll keep this in mind.
> --

- Start with single PC,
- then separate out the login/register database PC;
- then start adding as many PCs to do web access / file storage job as need=
ed;
- the web access /  file storage PC would either serve the request if
the file is available locally,
- or, if the file is not available locally, the PC would ask local
database about which servers keep the file, and then redirect to one
of them.
- the synchronization of the local databases shoud be performed over
resonable time interval;
- you don't need RAID in my opinion, just maintain multiple copies of
files and place PCs at different locations; HDDs are cheap now, 2TB
per server seems to be a reasonable option. With reasonable
motherboard, RAM, and case, the server would be cheap.
--=20
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.