-
Notifications
You must be signed in to change notification settings - Fork 379
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
Improve memory performance #195
Conversation
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.
Reviewed 3 of 3 files at r1.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @anurags92 and @karlmcguire)
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 is good to go.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @anurags92 and @karlmcguire)
@martinmr I have a test where I add a value to cache with TTL and then check for that value after TTL passed(say one second), that test is failing after this change(works fine with v0.0.3 ofc). I had to increase my wait time to make that test pass. I don't see any change that would do that in quick pass over code, but it would be a good idea to check SetWithTTL tests after this change. |
Alright, so did some testing with couple sha's around this change, and this change definitely has some kind of regression with TTL. |
hey @varun06 , can you share your test? Maybe send a PR to add it to ristretto? We can look at the failing test if this change has caused it. |
sure @jarifibrahim |
@jarifibrahim This is the test that's failing
|
so it seems that there is a regression when we use SetWithTTL. |
Related to DGRAPH-1378
This change is