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

We tried a hack to force flush to disk as early as possible but this broke everything so we stopped. We do try to untie as early as possible. Should I paste in the test scripts? They are a mess, admittedly, as they were thrown together from bits and pieces to prove a point.

It really looks like locking really fails for us in the scripts.
  • Comment on Re^4: Apache::Session problems under high load

Replies are listed 'Best First'.
Re^5: Apache::Session problems under high load
by borisz (Canon) on Oct 27, 2004 at 15:15 UTC
    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
      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