-
Notifications
You must be signed in to change notification settings - Fork 111
[runtime/utils/buffer] [storage/journal/fixed] buffer pool managed read caching for blobs #1157
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
|
I am getting the sense that "invalidating" pages if we wrap mutable buffers may not be that bad. Maybe I'm being optimistic. This could allow us to just add Write buffers under this thing, we could just call this |
I agree, just need to potentially maintain a dirty list of pages or something like that.
Yes if things work out these can be combined in interesting ways. |
ae2095b to
fde1ac4
Compare
I have added a cached blob type that allows writes, but only if they are appends. It's quite lightweight, so using that even when you could use an Immutable wrapper should be fine (not have much performance impact.). This way the buffer pool need only manage read-only data, which keeps things simple & fast. |
fde1ac4 to
bd092f2
Compare
b3b69f9 to
06a15ca
Compare
f5fef53 to
0554e3b
Compare
0554e3b to
83161c6
Compare
Codecov ReportAttention: Patch coverage is
@@ Coverage Diff @@
## main #1157 +/- ##
==========================================
+ Coverage 91.39% 91.45% +0.06%
==========================================
Files 218 221 +3
Lines 59455 59938 +483
==========================================
+ Hits 54338 54817 +479
- Misses 5117 5121 +4
... and 1 file with indirect coverage changes Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
Appendblob wrapper, providing random-access read caching and write caching for blobs that can be modified only through appends.prune()to no longer return the actual pruning position.