Does a big morph library slow DAZ studio down?

It happens that my G3F library is rather big already. Purchased all G3F figure pro packs, lots of morphs like Zev0s and various other figures.
As many of those products add stuff to the data-G3F-morphs folder I wonder whether this starts to slow things down. I have noticed that it seems to take more and more time to load a new G3F into a scene or to open a saved scene. Is that a known issue? Does the amount of installed products make DAZ studio slower?
And if so, are there any methods to improve things, like multiple run times which are not loaded if not needed? I install everything in one runtime via DIM though and have only one additional runtime for manual installs from other shops.
Thanks!
Comments
Simple answer is Yes.
DS has never liked loading thousands of little files, it's the main reason so many people had problems loading and saving with the old DAZ scene format, a large scene could have to deal with close on 100,000 files in the data folder.
The DSON system isn't much better, and it doesn't help that the figures are becoming bloatware, with a lot of "useless dummy files" making up a lot of the bloat.
I'm not sure what you mean here?
Head into your data folder, what you are looking for is any morph DSF file starting with "alias", all they create in an empty dial on a bone that has no mesh "attached" to it, instead they use ERC to link it back to the actual morph dial in the Body, which is where the mesh is.
All it does is give DS extra crap to deal with, just so the user base don't have to change how they do things, rather than forcing them to adapt to the differences between Poser and DS native content.
You may not have any use for aliases, but that doesn't make them in general "useless dummy files" since others may well find them a useful way of working.