this could have a rather important performance impact, has that impact been studied ? Is there an easy way to plug this session data into something else that postgresql ?
The perf. impact is not really important right now as we are seeking correctness. Hence, multiplying possible backends right now is not an immediate priority.
Note however that there exists a second patch stack providing a caching infrastructure for, amongst other things, session (usgin e.g. a memcached server).
Comments
-
2010/11/15 09:17
-
2014/04/29 15:33, written by alutz
-
2014/04/29 15:35, written by alutz
-
2014/04/29 16:33, written by acampeas
-
2014/04/30 19:33, written by cdevienne
-
2014/04/29 16:33, written by acampeas
add commentrequired for customer project.
this could have a rather important performance impact, has that impact been studied ? Is there an easy way to plug this session data into something else that postgresql ?
oh, and by the way, this feature would be great news for scaling cubicweb
Of course, that's the whole point :)
yep, this is why we (unlish) need it
The perf. impact is not really important right now as we are seeking correctness. Hence, multiplying possible backends right now is not an immediate priority.
Note however that there exists a second patch stack providing a caching infrastructure for, amongst other things, session (usgin e.g. a memcached server).