Restore browsing still slow on 2.0.3.3 beta

Support
21

250MB volumes, 500Kb blocks.

As far as I know, there aren’t any defaults that limit CPU usage to docker containers in unRAID. I do notice that while attempting to open a folder, I’m not really seeing much CPU usage–maybe 25% on a single thread that will occasionally jump thread to thread. Once in a while it gets 60-70% spikes.

22

That’s completely fine. Should reduce DB size which in turn should improve lookup performance.

23

I’m running 2.0.3.3 beta via a Docker container in unRAID 6.4.0 on a Core 2 Duo 3.0GHz w/8G RAM.

Unfortunately, I haven’t finished configuring everything so I’ve only got about 2.75G / 5k of source files over 50 versions resulting in a little baby 58MB sqlite file so this probably isn’t particularly useful but…

  • 5 seconds for Fetching path information (initial page load or change of version)
  • 1-3 seconds for all remaining folder expansions

To be honest, the 10 minutes for the initial Fetching path information to load sounds like old pre-updated restore code times.