You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 24, 2022. It is now read-only.
I read in the readme file that using the shared memory option for shared sessions adds a lot of complexity to gain some speed. This bothers me a bit and makes me feel that I should not enable this feature.
What if you just used memcached as an option for storing/retrieving shared session data? Would this make things less complex and still allow some speed gains? Or, would the overhead of interacting with memcached be too great to make this feature useless?
Anyway, I'm not a stud user yet as I am just researching, but thought I would make the suggestion.
The text was updated successfully, but these errors were encountered:
For local caching, it is dubious that adding memcached support would go anywhere near the performance of a shared memory segment. For remote caching, look at issue #29 for a discussion about this.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I read in the readme file that using the shared memory option for shared sessions adds a lot of complexity to gain some speed. This bothers me a bit and makes me feel that I should not enable this feature.
What if you just used memcached as an option for storing/retrieving shared session data? Would this make things less complex and still allow some speed gains? Or, would the overhead of interacting with memcached be too great to make this feature useless?
Anyway, I'm not a stud user yet as I am just researching, but thought I would make the suggestion.
The text was updated successfully, but these errors were encountered: