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

I think even more that you think wrong on the locking issue. Try to add a Transaction => 1 to your tie, this is more likely what you want.
Boris
  • Comment on Re^5: Apache::Session problems under high load

Replies are listed 'Best First'.
Re^6: Apache::Session problems under high load
by perrin (Chancellor) on Oct 27, 2004 at 17:03 UTC
    That won't do much with MySQL.
      It does, It get the sessionlock direct inside new and not at the writeback stage. That may resolve the issue that the anonmonk has, since there is no race between the concurent requests.
      Boris
        It does what you say, but not for MySQL. From the docs:
        Note that the Transaction argument has no practical effect on the MySQL and Postgres implementations. The MySQL implementation only supports exclusive locking, and the Postgres implementation uses the transaction features of that database.