/temp_folder is a "mount point" (see your zope.conf file).
Whether or not you put a session data container inside of a temp folder, you may get better conflict-related performance out of "faster", a drop-in replacement for the stock Zope sessioning machinery... see http://www.agendaless.com/Members/tseaver/software/ faster/ (but you might not, it depends on the sessioning access pattern). In particular "faster" is much better conflict-wise when sessions are accessed but not changed in the course of a request.
- C On Jun 24, 2007, at 8:19 PM, Manuel Vázquez Acosta wrote:
Hi all, I have been digging into Session Management in Zope, because is causing a little overhead. We have develop a Plone Application, which must respond to 30 concurrent user every 12 seconds, we have setup CacheFu and Squid for this. We have used OpenSTA to stress test the application. When we run the bench for a non login test, everything goes just fine. But when run a bench in which a user logs in, we observe too many ConflictErrors, which, I thinks, slows too much the application, because zope retries the request 3 times. I have read /temp_folder is RAM based folder, and also that it should be a MountPoint, but looking at the code and with the help of DocFinderTab, I have found /temp_folder is a Products.TemporaryFolder.SimpleTemporaryContainer, which seems to be just a folder in the ZODB... This sould be this way? Does /temp_folder/session_data is the RAM based storage? Best regards, Manuel. _______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
_______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )