-
Notifications
You must be signed in to change notification settings - Fork 365
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
use in memory cache in parallel with db cache, convert keys to be date specific #8563
Conversation
355088b
to
fab8e01
Compare
I have tests- ready for review. |
82ab491
to
ef049b5
Compare
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.
Do you plan to migrate the old line cache?
I have updated the code- when finding no this is simple and lightweight. |
hmm, somehow I got a bunch of additional files/changes mixed in with this; no idea why |
all ready for review! |
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.
Approved but will push it to prototype instance before merging.
8e9fd77
to
f0c52f4
Compare
with the latest commit to the stack a few things are solved:
|
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.
This has been pushed to prototype.
This broke bug suggestions on prototype:
|
my most recent commit does:
|
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.
Pushed to prototype one minute ago.
I still see this error |
Jenkins says the top of this patch stack got deployed shortly before 20:12 UTC. There have been issues with older pushes getting deployed in the past but this was fixed a few weeks ago. The issue was some keys had duplicate root prefixes. I have deleted all caching data on prototype and the cache gets populated again. The spinner in the failure lines are persists because of an internal issue with |
I want to figure out how to test this. Also some of this might be a little overkill.