Re^9: Apache::Session problems under high load

in reply to Re^8: Apache::Session problems under high load
in thread Apache::Session problems under high load

But the 'exclusive locking' is what the monk want. IMHO. And Apache::Session does that if 'Transaction => 1' even when this is no real transaction, it prevents others to write to that session until the session is untied. Whereas without 'Transaction => 1' another request can overwrite the sessiondata with older data.

Boris

Comment on Re^9: Apache::Session problems under high load

Replies are listed 'Best First'.
Re^10: Apache::Session problems under high load by perrin (Chancellor) on Oct 27, 2004 at 19:15 UTC
You're missing the point. If he is using Apache::Session::MySQL he already hasexclusive locking. It has no other mode and is totally unaffected by the `Transaction` option. The same goes for Postgres and Oracle. So, it's best to find out which one he's using before offering this advice, because it may not do anything at all.	[reply] [d/l]

In Section Seekers of Perl Wisdom