-
Notifications
You must be signed in to change notification settings - Fork 897
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Performance: Do not schedule Session.purge if this Session is not used #15064
Performance: Do not schedule Session.purge if this Session is not used #15064
Conversation
You can use memcache or SQL session. When you use memcache this whole job does nothing. Just inserts into a queue, updates queue, selects empty from Session and then removes from queue. This also frees up some memory and scheduler cycles. Yaix! Note, we already require users (in documentation) to restart EVM server when they change session store (so we can do this).
d179c7e
to
d393bef
Compare
Checked commit isimluk@d393bef with ruby 2.2.6, rubocop 0.47.1, and haml-lint 0.20.0 |
@imtayadeway, @gtanzillo : any reason not to merge this one? Makes sense and the code looks good to me. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 I'm good with this change
This has minimal to no performance impact - 1 query returning 0 records. And, it is also only applicable to customers running with AR sessions (basically if they are running a load balancer) I would like to backporting to |
Sounds good. Cheers! 🛀 |
Actually to do this nothing job we need to:
And now ... let me count the syscalls... |
@kbrock Is there a BZ for this? Need a BZ to backport to Fine branch... |
…n-is-turned-off Performance: Do not schedule Session.purge if this Session is not used (cherry picked from commit 493a488) https://bugzilla.redhat.com/show_bug.cgi?id=1510054
Fine backport details:
|
…f-session-is-turned-off Performance: Do not schedule Session.purge if this Session is not used (cherry picked from commit 493a488) https://bugzilla.redhat.com/show_bug.cgi?id=1510054
You can use memcache OR SQL session. When you use memcache this whole job does nothing. Just inserts into a queue, updates queue, selects empty from Session and then removes from queue.
This also frees up some memory and scheduler cycles. Yaix!
Note, we already require users (in documentation) to restart EVM server when they change session store (so we can do this).