aawsome

Thanks for opening this issue @zumm We can for sure add the needed information to the repository, but this is not the main focus for the core maintainers. Anyone up...

@borkd Thanks for reporting! Now, this is an issue I'm very much interested in fixing as one of rustic's promise is to use less memory than restic. However, I have...

Thanks for your results! Now, memory usage is very fine. And I'm also very satisfied with user CPU. But system CPU is very high - especially compared with restic. Moreover...

Here are my numbers from a ~200GB repo (local, without cache): `restic check`: ``` 85.71user 2.80system 0:47.30elapsed 187%CPU (0avgtext+0avgdata 239752maxresident)k 6328inputs+8outputs (39major+66427minor)pagefaults 0swaps ``` `rustic check`: ``` 40.84user 5.12system 0:31.00elapsed...

I tested to use the jemalloc allocator. In my case this did speed up rustic a bit, but left system cpu time and minor pagefaults still high. There is now...

Closing this as there seems to be no performance problem ATM. If you encounter any similar or other performance topic, feel free to open a new issue !

@seiuneko Can you please give the exact calling parameter you use when when running restic (in resticprofile) and rustic? And the outputs of both runs? The higher memory usage can...

> To have a full picture would it be possible to include uncompressed data stats as well? Effectively the same as now but uncompressed sizes. In fact it is not...

@kapitainsky I added a few more statistics. The output now looks like this:

I'll add this output to the ls view (of course only showing the current tree and no diff stats) and the snapshots view (with the possibility to get statistics about...