At 14:15 24.11.2002, Jean-Christian Imbeault said:
--------------------[snip]--------------------
>Oh, this site is just your regular, run-of-the-mill, amazon.com copy.
>
>For each open session I store up to 20 variables. It's not a lot, but
>each access to a script means a disk read/write so they will eventually
>add up if there are enough users.
>
>Of course this problem goes away if you throw enough money at the
>hardware ...
--------------------[snip]--------------------
Assuming you're running a server operating system (either Linux, or other
X, or even Win2K _server_) disk i/o gets already greatly reduced by the OS.
Any server OS implements its own decent file i/o cache that leverages
repeated disk i/o transparently. I wouldn't bother about that too much.
What you should keep in mind that the OS needs enough memory to build up
its decent cache. Which would mean that you plug in more memory banks the
more users you have. If you suspect your server is slowing down because of
disk i/o why not run a realtime performance log to see where bottlenecks
are, and to act accordingly then?
My experience shows that file session storage is the very last bottleneck
that ever would occur; the database times add up much quicker than any
session file i/o would ever be able to.
--
>O Ernest E. Vogelsinger
(\) ICQ #13394035
^ http://www.vogelsinger.at/
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
