We're using Apache::Session::MySQL (Apache::Session 1.54) and occassionaly see long lock times.
Also, we'll soon be adding a substantial number of users to our system and I wonder if it would be wise to move away from the table locking that is currently being used with Apache::Session::MySQL. I'm looking at Apache::Session::Flex and setting "Lock=>'Null'"...however, I get the impression from an old email (see below) that Flex is for debugging only. First, any benchmarks on what kind of load I can realistically use with Apache::Session::MySQL? Is moving to Apache::Session::Flex a good choice (and then we could also change the session table to INNODB), or should I create my own Apache::Session::MySQL-type module by changing Lock => 'Null'? I didn't see much discussion on this in the archives, so if it is there, please point me to the thread... Thanks... -- > On Thu, 11 Oct 2001, Jeffrey W. Baker wrote: > >Regarding Flex, nobody uses it. It is for debugging. >If you have a >particular variant of Flex that you use all the time >(very likely), you >can code up a 6-line module to make a real >implementation like all the >other session modules. > >Flex is for debugging, period. __________________________________________________ Do you Yahoo!? Yahoo! Tax Center - forms, calculators, tips, more http://taxes.yahoo.com/
