|
|
Posted by shimmyshack on 05/01/07 12:51
On May 1, 5:58 am, blessblessbl...@gmail.com wrote:
> thank you you two.
> i understand now that it will run the image locally and only display
> the thumb.
> but what is this stress on database, as of when is it considered
> stressful? when loading 20 thumbs at the same time? or when hundreds
> of people look at it at the same time?
> this is just for a private portfolio of a photographer. so its not
> aimed at the masses.
> will this picture be stored temporarily on a private persons computer
> like with normal images, or will it load new every a person visits the
> page another time?
> bless
you will be lucky if you can get 100 simultaneous requests! actually
most simple (non-load-blanced) web servers wouldnt handle that many.
the stress would come if each picture was large, not because the
database couldnt handle them - after all a table is a file somewhere
on a filesystem, but because if the database lives on another machine,
you will have to set up a TCP connection, and retrieve the data across
the network, then output to the client.
SQL was designed partly to stop the need for huge chunks of data
travelling across the network to be sorted, instead SQL sorted the
data and only sent what was needed. In the same way, /IF/ you organise
your pictures properly on the local filesystem (N directories each
with a sensible max limit, a non system disk for pure data storage
etc. etc..), set up the web server properly, retrieval will be faster,
perhaps easier to maintain and backup.
however as you scale up you will find your pictures are "non-local"
anyway, so a distributed database is an equivalent option after all!
Navigation:
[Reply to this message]
|