https://bugs.kde.org/show_bug.cgi?id=426965
--- Comment #4 from Milian Wolff <m...@milianw.de> --- OK that's a huge amount of data, which corresponds to a ton of allocations... I mean just for the fun of it, try to do something like this: zcat <yourfile> | grep -cE '^[\+-]' That will give us the number of allocation events. I suspect this to be a _very_ large number. As a workaround, until we find some improvements to this, here are some suggestions: - only track a smaller workload for your application, i.e. reduce the problem size, or the duration for which you are tracing - use runtime attaching to ignore the startup phase if that is allocation heavy Otherwise, I'm afraid to say that zstd is the only quick thing you could try. It's much faster at decompressing the data compared to gzip, so that will be noticeable to you. But in the end we'll still have to crunch through 65GB of data, which just takes a really long time... -- You are receiving this mail because: You are watching all bug changes.
