I want like to be kept in on this, if you find any solutions to speed up.
I also posted a fair while ago, about the types of errors VaM, spits out in the log, one error actually prevents loading all VARs into the Scene browser.
I also suspect this is effecting loading times
there are two types of errors
1. wrong naming.. where vars must be creator.scenename.version
2. corrupt vars.. the error displayed in the LOG is really weird.. it's these that are causing vam to not load the VAR totally.
Loading times are heavily effected by Morphs, so v.20.0 having heaps of vars with heaps of morphs internally.. then having heaps of morphs in custom folder would be huge slow downs
the beta solves this and improves the loading maybe by half.. maybe further optimizations will come.
I don't think the creator expect so many var
So I ran vam into a sandbox and traced all file access (950'000 lines to look at..). Rough analysis:
Loading time of VAM independently of vars is strange, small reads of files in VAMdata.
Then obviously VAM parses all vars, prefs, fav, .. but it seems rather fast.
I haven't seen particular VAR creating problem (but I'd need to plot time differences between vars..)
On my particular installs:
Bad files have been rmoved: wrong naming, corrupted ones (broken zip format). I don't think they affect much time as it didn't change much. Also had one with circular dependencies (A requests B and B requests A).
I also removed massive var which include others content.
So I can't tell you which ones, I erased them already.
I also removed all custom old format files (300GB).
Overall it didn't change much.
In the end, for reference, I have 120GB within 2500 vars.
Windows: Stupid defender keps on scanning a 120KB file which is from.. Microsoft. Also search indexing tries to index content of var (I associated .var with 7Zip, I wouldn't advice doing that) and also pdf (I have a few hundreds and some are 40MB+).
So... at first glance, it just seems to be the amount of vars that influence loading time.