Use native zarr for trace worker instead of xarray for memory efficiency.#710
Merged
tasansal merged 7 commits intoTGSAI:mainfrom Oct 13, 2025
Merged
Use native zarr for trace worker instead of xarray for memory efficiency.#710tasansal merged 7 commits intoTGSAI:mainfrom
zarr for trace worker instead of xarray for memory efficiency.#710tasansal merged 7 commits intoTGSAI:mainfrom
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #710 +/- ##
==========================================
+ Coverage 85.30% 88.87% +3.56%
==========================================
Files 46 84 +38
Lines 2219 4529 +2310
Branches 306 294 -12
==========================================
+ Hits 1893 4025 +2132
- Misses 281 435 +154
- Partials 45 69 +24 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
zarr for trace worker instead of xarray for memory efficiency.
this will trigger CI/CD to make a new release, better not done here, but must be done from `main`
2ba7c92 to
104507c
Compare
tasansal
approved these changes
Oct 13, 2025
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.
When scaling segy ingestions we observed higher than expected memory usage. I believe this is in part due to unavoidable overhead in the Xarray API internals. For that reason I have begun to strip out xarray API calls in favor of zarr.
This appears to have helped reduce large scale memory usage, although it is still consuming more memory than expected.