Am 21.05.2013 11:41, schrieb Cor Bosman:
the system would be much more scalable and is much more scalable with *not* using MySQL for storing sessions and RC is performance wise the weakest part of the whole infrastructure
You probably have a different view of what it means to be scalable than the rest of the world. Scalable means you can add more servers to handle the load. Using a ramdisk is about the least scalable thing you can do. It's great for performance, not so great for scalability.
what are all this discussions for?
having a customized session handler *mandatory* is dumb damned it *creates additional load* where zero load is by disk IO and by CPU cycles for php code
in the first front scaleable is how many users can i serve and with my setup i can serve much more than with a mysql session handler which prodcues IO loads
you do not need to care about my servers, the are running on a vSphere cluster and have anough ressources for the next years
- no session file locking (parallel requests do not wait)
and no integrity and cleanups or how do you explain me the 5000 records in the session table on a server with a few users after some months?
I have no such issues. Our session table looks sane to me. My oldest session entries are 5 days old
because you most likely have php default settings
RC is currently the only webapp not running sane with 100% customized environment because it does things which should not be done by the webapp and if somebody has to configure session-handlers it is the admin and nobody else PERIOD