If memcached is used as session engine, then session get and set will make a network request to whatever server is configured, I assume. Which is slower than first getting the entire session, then modifying it throughout the application, then saving it, as an after-template hook for example. But I do not see an operator to set an entire session? or is that a wrong-headed idea anyway? Niels Larsen http://genomics.dk (The memcached storage engine interface crashes, but is being fixed, Sawyer X wrote earlier. And this is, for me, not an urgent question, just curious).
2011/10/3 Niels Larsen <niels@genomics.dk>:
If memcached is used as session engine, then session get and set will make a network request to whatever server is configured, I assume. Which is slower than first getting the entire session, then modifying it throughout the application, then saving it, as an after-template hook for example. But I do not see an operator to set an entire session? or is that a wrong-headed idea anyway?
So you want to cache your access to the cache engine? :) Well, not sure that's really worth the effort, at least semantically.
On Mon, 2011-10-03 at 14:41 +0200, Alexis Sukrieh wrote:
2011/10/3 Niels Larsen <niels@genomics.dk>:
If memcached is used as session engine, then session get and set will make a network request to whatever server is configured, I assume. Which is slower than first getting the entire session, then modifying it throughout the application, then saving it, as an after-template hook for example. But I do not see an operator to set an entire session? or is that a wrong-headed idea anyway?
So you want to cache your access to the cache engine? :) Well, not sure that's really worth the effort, at least semantically.
I have no test numbers, just a thought, but my guess is it will matter a great deal. Without new semantics, what is the best way to set an entire session in todays version? (I am a perl veteran who cannot dance yet).
participants (2)
-
Alexis Sukrieh -
Niels Larsen