-
Notifications
You must be signed in to change notification settings - Fork 4
Track latency of per item eviction/promotion between memory tiers #91
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
Conversation
6b16096
to
6da0627
Compare
6da0627
to
4d5ba92
Compare
4d5ba92
to
1086394
Compare
1086394
to
7c4c6cf
Compare
util::RollingLatencyTracker rollTracker{ | ||
(*stats_.classAllocLatency)[tid][pid][cid]}; | ||
|
||
util::RollingLatencyTracker rollTracker{(*stats_.classAllocLatency)[tid][pid][cid]}; |
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 assume this will still track latency for both user and bg allocations? If yes, it would be nice to put some comment regarding that.
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.
We're not tracking rolling average latency for background threads separately. This feature is not in use anywhere. It was meant to provide a low overhead tracker for profile-driven batch evictions. Profile-driven approach has not been explored since Daniel Obiri worked on it a year back and found it didn't provide any significant improvement. I'm not sure Meta will accept the rolling stats upstream PR - it has not been reviewed yet.
ae2f3ec
to
8d2c390
Compare
This change is