https://bugs.kde.org/show_bug.cgi?id=426965
Milian Wolff changed:
What|Removed |Added
Resolution|--- |NOT A BUG
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=426965
--- Comment #4 from Milian Wolff ---
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 | grep -cE '^[\+-]'
That will give us the number of allocation
https://bugs.kde.org/show_bug.cgi?id=426965
--- Comment #3 from Andrew Somerville ---
Looks like I got the original number wrong it's 4gb compressed with gz (and
65GB uncompressed! geeze) I'll try switching to zstd and see what the speed
looks like.
Also I started adding some information to the
https://bugs.kde.org/show_bug.cgi?id=426965
--- Comment #2 from Milian Wolff ---
Is the 8GB file compressed or uncompressed? It sounds like it's uncompressed -
try to compress it via `zstd` to create a `*.zst` file - that greatly reduces
the disk-I/O time and should make things considerably
https://bugs.kde.org/show_bug.cgi?id=426965
--- Comment #1 from Andrew Somerville ---
Addendum:
* Loading takes 10s of minutes in the case of an 8GB file.
* Unintentional process terminations (crashes, accidental window close) are of
particular issue for heaptrack_gui
--
You are receiving
