Closed saraadams closed 10 months ago
Instead of reading the Bazel profile all at once, use a stream to reduce memory consumption.
Benchmark with a Bazel profile of unzipped size 357MB Using YourKit as a profiler and checking the shallow size at the end of the BazelProfile constructor:
BazelProfile
Before: 3.6 GB After: 349 MB
Contributes to #163
Instead of reading the Bazel profile all at once, use a stream to reduce memory consumption.
Benchmark with a Bazel profile of unzipped size 357MB Using YourKit as a profiler and checking the shallow size at the end of the
BazelProfileconstructor:Before: 3.6 GB After: 349 MB
Contributes to #163