Just to keep this up-to-date, now the startup-used-space-filewalker, aka piece-scan-on-startup, scans each satellite’s data folder one by one, meaning it first scans for US1, then EU1, etc. I don’t know the exact order, so don’t quote me on this. You shoud see in the log:
piecescan started for sat ID xxxx,
piecescan finished for sat ID xxxx,
piecescan started for sat ID yyyy,
piecescan finished for sat ID yyyy, etc.
Second, there is a new system to speed up the second scan; it’s called badger db or badger cache, and it’s a database for matadata cache. The first scan takes the usual time and it caches the matadata, but the second scan will start first by reading the badger db, than continue scanning the rest of the files if the first scan was interrupted.
So it acts like a cache and a progress saver. This cache speeds the piecescan exponentialy, but it works best if it is stored on another drive, a SSD or NVMe.
And is still in a beta, so hickups might crash your node from time to time. That’s why is not enabled by default. Search the forum for badger cache. You should turn off the lazzy mode if you enable badger.
1 Like