Ncdu: An Updated Fork

14 pointsposted 11 hours ago
by rcalixte
(github.com)

6 Comments

dawidpotocki

3 hours ago

I have personally moved to gdu (https://github.com/dundee/gdu) as I found it to be way faster than ncdu (I haven't checked the fork but I don't expect it to improve that much).

1 minute vs 1 second for my entire / which includes mounts to NFS shares (used 1.4 TiB on host SSD, 14 TiB on NFS HDDs and 3 TiB on NFS SSD).

miduil

2 hours ago

Could you do me a favor and test with

   ncdu -t32
this uses 32 threads and should be much faster. I think only reason this isn't default is to be a friendly tool on your host.

dawidpotocki

2 minutes ago

It's been going for 5 minutes already… I can't be bothered to let it run longer.

Seems to be wasting a lot of time scanning `/run/user/1000/doc` from Flatpak.

rcalixte

11 hours ago

This project carries significance for me, not only as a learning resource but also for future projects which is why I've forked and will aim to maintain it for the foreseeable future. I'm still getting familiar with the codebase beyond what was required to update it so any potential issues will be handled on a best-effort basis. I didn't see any actionable issues in the issue tracker but that doesn't mean there aren't things that can be implemented or improved upon. I aim to implement some form of CI/CD at some point as well.