Am 18.04.2016 um 06:04 schrieb Jonathan Vanasco:
I use a heavily forked version of pyramid_redis_sessions. the actual distribution hits redis way too much and caused bottlenecks for us. it uses multiple calls when only one is needed, and sets a new expire on every attribute access (only one is needed per request, or redis could be configured as a LRU cache and no expires are needed).
Right, it would make sense to leave the expiration handling to Redis. Another possible improvement of pyramdid_redis_session would be to also support Vedis (vedis-python) which works like Redis but doesn't need an additional server component. For most apps this could suffice even in production and you could still easily upgrade to Redis using a config setting if you're hitting a limit.
-- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/pylons-discuss/57148A2D.4030509%40online.de. For more options, visit https://groups.google.com/d/optout.
