Repository navigation
Add benchmark tables comparing e57 with pye57 to the README - #53
Merged
Merged
Conversation
mohsaad
marked this pull request as ready for review
November 15, 2026 18:06
Adds a Performance section to the README with read time, peak memory, output size and overhead for e57 0.2.3 and pye57 0.4.19. It covers a real 27.8M-point scan and synthetic files of 50M and 1B points, on Apple Silicon and on an AWS r7i.8xlarge. pye57 is shown with both a naive np.concatenate merge and a preallocated merge, since its peak memory depends heavily on how scans are combined. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
mohsaad
force-pushed
the
docs/benchmark-tables
branch
from
November 15, 2026 21:08
a65cce9 to
03268c1
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Relates to #21 (RAM usage).
Adds a Performance section to the README. It compares
e570.2.3 with pye57 0.4.19 on read time, peak memory, output size and overhead (peak memory divided by output size).What's measured
gargage.e57from the libE57 example data, 1 scan, 27.8M pointsread_pointsreturns: all scans merged, pose applied, invalid points dropped.np.concatenatemerge and with a preallocated merge. The merge strategy changes its peak memory a lot: 60.5 GiB naive vs 33.0 GiB preallocated at 1B points.Summary
e57adds almost no memory on top of its output (1.00–1.02×). On a file with one big scan it uses about 2.6× less memory than pye57.e57, mostly becausee57returns color as float32 (12 bytes per point vs 3).The README presents these results as they are, including where pye57 does better. Converting color to uint8 or making the color type optional would close most of the memory gap at large sizes. That could be a follow-up if you're interested.
Notes
benchmarks/or link to it if you'd like the tables to be reproducible from this repo.e570.2.3 as it is onmain. Fix missing color/intensity when a file has invalid points #50 only changes how buffers are sized, so it shouldn't affect them much, but I haven't measured it.🤖 Generated with Claude Code