No, the cache files in OXID EE are generated once and in standard configuration have a lifetime of 12 hours. The users only "read" this file once it is generated, it's a static file (or object, depending on cache backend). Performance peak is only when generation is necessary. Users with session have their "own" cache files so much more generation is needed and hits for existing cache files decreases. Regards, Elisabeth
Von: [email protected] [mailto:[email protected]] Im Auftrag von Shaun Purvis Gesendet: Mittwoch, 17. August 2011 16:10 An: [email protected] Betreff: Re: [oxid-dev-general] Why starts OXID a session only under special circumstances? Doesn't the example given by Elisabeth encourage session use for performance? If all users without a session share the same cache file, that would cause a bottle neck for write access? Since hard drive space is not usually an issue, seems to me that having more files per user would benefit performance. Am i missing something here? Regards, Shaun. On Wed, Aug 17, 2011 at 8:33 AM, Elisabeth Heckmann <[email protected]<mailto:[email protected]>> wrote: Hi, have a look at the function _getRequireSessionWithParams() in class oxsession. You can expand the array in config.inc.php and add classes, functions or parameters, so you are not bound to these conditions. Cause of performance reason it's a good idea to start session only when necessary. For example if you use caching in OXID EE all users without session use same cache file. Best regards, Elisabeth Heckmann ******************************************* shoptimax GmbH Guntherstraße 45a 90461 Nürnberg Amtsgericht Nürnberg HRB 21703 GF Friedrich Schreieck Tel.: 0911/25566-17 Fax: 0911/25566-29 [email protected]<mailto:[email protected]> http://www.shoptimax.de ******************************************* -----Ursprüngliche Nachricht----- Von: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] Im Auftrag von Stefan Krenz Gesendet: Mittwoch, 17. August 2011 13:07 An: [email protected]<mailto:[email protected]> Betreff: [oxid-dev-general] Why starts OXID a session only under special circumstances? Hi, OXID starts a session only when a special class or function is called or a parameter exists in the request. Classes that cause OXID to start a session: - register (in views/register.php) - account (in views/account.php) Functions that cause OXID to start a session: - tobasket - login_noredirect - tocomparelist Other request parameters that cause OXID to start a session: - _artperpage - listorderby Currently developers are bound to these conditions to start a session and store variables. Because oxsession is NOT overloadable and the configuration variable 'aRequireSessionWithParams' is only used in 'core/oxsession.php'. Why is the session start bound to these conditions? Regards Stefan Krenz -- Stefan Krenz Mayflower GmbH Pleichertorstraße 2 Tel.: +49 931 359 65 1163<tel:%2B49%20931%20359%2065%201163> D-97070 Würzburg Fax : +49 931 359 65 28<tel:%2B49%20931%20359%2065%2028> [email protected]<mailto:[email protected]> http://www.mayflower.de Mayflower GmbH, Standort Würzburg Firmensitz: Mannhardtstraße 6, 80538 München Registergericht: Amtsgericht München, HRB 142039 Geschäftsführer: Gregor Streng, Björn Schotte, Albrecht Günther, Johann-Peter Hartmann _______________________________________________ dev-general mailing list [email protected]<mailto:[email protected]> http://dir.gmane.org/gmane.comp.php.oxid.general _______________________________________________ dev-general mailing list [email protected]<mailto:[email protected]> http://dir.gmane.org/gmane.comp.php.oxid.general
_______________________________________________ dev-general mailing list [email protected] http://dir.gmane.org/gmane.comp.php.oxid.general
