-
Notifications
You must be signed in to change notification settings - Fork 999
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
recognizing hot keys #257
Comments
Algorithms that might help: we should choose the simpler one, not necessarily the most sophisticated one. |
after reading these paper I think it's better to start with HeavyKeeper. |
I have read the heavykeeper paper and am implementing a heavykeeper structure that does not use min-heap. The basic idea for dragonfly to introduce hotspot awareness is to set one heavykeeper per proactor and perform sorting to find the hottest few keys when hotspot information is needed. I intend to do the following. First I will focus on the implementation and testing of heavykeeper, and continue to dive into dragonfly's code, subsequent questions may need to be discussed by community members. This is not something that can be done quickly, so I think these ideas will appear in many PRs that |
@Super-long please join our Discord server https://discord.gg/HsPjXGVH85 and say hello. I will add you to our #dev channel. |
Part of the heavy keeper algo, required for #257. Signed-off-by: Roman Gershman <[email protected]>
Part of the heavy keeper algo, required for #257. Also see #446 for the initial (abandoned) PR. Signed-off-by: Roman Gershman <[email protected]>
Part of the heavy keeper algo, required for #257. Also see #446 for the initial (abandoned) PR. Signed-off-by: Roman Gershman <[email protected]>
Part of the heavy keeper algo, required for #257. Also see #446 for the initial (abandoned) PR. Signed-off-by: Roman Gershman <[email protected]>
Motivation: https://blog.box.com/introducing-memsniff-robust-memcache-traffic-analyzer
for large scale deployments, caching teams would like to learn about hot keys in real-time so that they could handle them in a special way.
Currently, teams develop sniffers! (see the link) to do so. It's not very elegant way and very CPU intensive. We could integrate it into DF and provide native support for this.
The text was updated successfully, but these errors were encountered: