-
Notifications
You must be signed in to change notification settings - Fork 976
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
Query cache seems to be limited to ~2.1GB #2815
Comments
Another thing of note, I've also noticed that the cache reports several Extabytes of cached memory sometimes, it seems that it does this whenever it passes 2^31. Presumably then triggering the purge to start. In my graph above I filtered out items less than 1e12 to see the graph better but gaps there are times when the reported cache jumps so high. |
Looking at the code a bit, I think this may be the issue here: Lines 296 to 304 in f02efa2
I would think r would also need to be a uint64_t
|
hi @mknapphrt . |
Yes! Thanks for the review! |
We've set the query cache size to be 4095MB (just shy of 4096 because we're currently running version
ProxySQL version v1.4.10-1-g5eb0f3e, codename Truls
in production which doesn't yet have the fix #2040). But it seems that we're currently bound to ~2.1GB, and once that's hit a bunch of cache entries are being purged all at the same time. Easier to visualize w/ some prometheus graphs:We've got machines w/ way moee than 2Gb of ram and we'd like to utilize more of it for caching. Possibly there's other configurations that we're missing that need to be tweaked too?
We tried using the newest release 2.0.12 just now to see if this was addressed and it doesn't seem to be, we experienced the same results.
Here are the cache related settings we're running w/:
OS Version: debian 9.11, 4.19.92 kernel version
I don't see any log files in our data dir or any output in the journal, happy to provide logs if someone can advise where to find them.
The text was updated successfully, but these errors were encountered: