Skip to content

[ntuple] Save a memcpy when reading a compressed Anchor in RMiniFile #18612

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

silverweed
Copy link
Contributor

Do:
(read into unzipBuf) -> (unzip into finalBuf)

instead of:
(read into finalBuf) -> (unzip into unzipBuf) -> (copy back to finalBuf)

Checklist:

  • tested changes locally
  • updated the docs (if necessary)

Do:
  (read into unzipBuf) -> (unzip into finalBuf)

instead of:
  (read into finalBuf) -> (unzip into unzipBuf) -> (copy back to finalBuf)
@silverweed silverweed requested review from hahnjo and enirolf May 6, 2025 07:24
@silverweed silverweed self-assigned this May 6, 2025
@silverweed silverweed requested a review from jblomer as a code owner May 6, 2025 07:24
Copy link

github-actions bot commented May 6, 2025

Test Results

    19 files      19 suites   4d 12h 9m 36s ⏱️
 2 731 tests  2 731 ✅ 0 💤 0 ❌
50 456 runs  50 456 ✅ 0 💤 0 ❌

Results for commit b81ea42.

♻️ This comment has been updated with latest results.

// Unzip into the final buffer
RNTupleDecompressor::Unzip(unzipBuf.get(), objNbytes, key.fObjLen, ntuple);
} else {
ReadBuffer(ntuple, objNbytes, offset);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't really think this is on the critical path, and now we have two calls to ReadBuffer...

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What do you mean two calls? They're mutually exclusive so we only have one; we're simply doing one less operation in one of the branches.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are two lines of code where we call ReadBuffer, which we will have to make sure updated in sync. That current code is more maintainable.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is ReadBuffer harder to maintain than memcpy? That too needs to be synchronized, and both are trivial things to do

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Skipping a useless mempcy can be a significant performance difference, for example in case of tight looping over a single branch and is worth the slight extra complexity.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This code is about the anchor which is read once when opening the file. There is simply no performance implication in that.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

which btw also means that the amount of memory copied is 78 bytes...

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I missed that ... indeed for such a low size ... even doing the compression is debatable ....

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For RMiniFile, this was explicitly implemented in 7b03bcc. I believe TFile always attempts compression and goes with it if beneficial, ie compressed size smaller than uncompressed.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change is not about performance at all, it's about code simplicity and straightforwardness. This code does less work and therefore is simpler to understand. However if I'm the only one who thinks so, this PR can be closed and not much of value would be lost, being such a small change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants