-
Notifications
You must be signed in to change notification settings - Fork 18
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
[RNTuple] Roadmap of writing RNTuple to disk #336
Comments
I have fully mapped every byte in a file now. @tamasgal might be interested in this: |
Haha awesome work Jerry! I still have not seen any RNTuple in our experiment but it's a good feeling that you shed so many light on this area :) |
I expect them to show up after ROOT team freezes them this year/early next year. (1.0.0) |
We should add this to our documentation as the golden reference ;) |
Regarding magic 6 bytes before RNTuple anchor: |
My current plan is to break this huge task into four large stages:
Stage 1 (Before July 2024)
In Stage 1 we aggressively use dummy data (raw bytes copied from real root files) and try to figure out what are the big-stroke steps we need when writing RNTuple to disk. Roughly they should be:
Usability after Stage 1:
bare minimal, user can write out primitive fields that are not too long.
Stage 2 (Before Oct 2024)
In Stage 2 we try to peel off dummy stuff in two ways:
At this stage we will still be very rigid when it comes to schema complexity, but closer to production quality in the "file size" aspect.
Usability after Stage 2:
Basically functional for very simple data schema up to any size, as long as it fits in RAM (one-shot writing)
Stage 3 (Before June 2025)
In Stage 3 we will expand the level of completeness in two critical ways:
Usability after Stage 3:
This will be analysis production ready -- users can write nanoAOD-kind of files with any size and can append to existing dataset, this will be the medium milestone for a production-level useful RNTuple writer
Stage 4 (unknown time)
In Stage 4 we try to complete whatever is still missing, possible items:
The text was updated successfully, but these errors were encountered: