On 6 June 2010 13:38, Chris Cormack <chris@bigballofwax.co.nz> wrote:
2010/6/5 Fouts, Clay <cfouts@ptfs.com>:
I can also attest to the benefit of storing session data somewhere other than in the MySQL database. LLEK has the ability to store its session data through memcached instead of writing to a file (which can create problems in a multi-server configuration) or MySQL. This frees up the database more than one might expect. The constant stream of tiny, non-contiguous INSERTs and UPDATEs contributes heavily to fragmentation of InnoDB writes which in turn lengthens transaction times. (Not to mention Koha's inability to selectively cull stale sessions, causing your table to have millions of rows over time). The drawback is of course that if memcached goes away you lose all your current session data since it's not a permanent storage medium, but this is not a significant loss in most circumstances.
Storing as temp files on a ram based disk as has already been suggested works much the same way too. Of course a patch for using memcached for session storage would be gratefully accepted and would save on once again doubling up on work already done.
This code is now in the Koha git repository, I'm not sure if it is implemented the same way in LEK, but it's now in Koha anyway. http://git.koha-community.org/gitweb/?p=koha.git;a=shortlog;h=refs/heads/new... Chris