I have pinned down my slow starts to QtGui4.dll taking forever to initialize.
Looking over the Qt dev forums, it seems that there was a similar issue, on some systems a few versions back. There didn’t seem to be a ‘fix’ for it, as it ‘went away’ in later versions or it could be ‘solved’ by rolling back to the previous version. It could also be eliminated by rebuilding the Qt libraries (compiling from source) on the affected systems
So, basically, it boils down to something about the specific build of Qt in 4.5 not being happy with my system…not enough to crash, in fact it is very stable…I’ve only had 3 crashes and 2 of those were the results of ‘torture testing’ and the third as an out of memory crash (Note to self: don’t turn off the limits on subdivision and then try to subdivide a simple cube 16 times…it WILL eat ALL of your RAM and then crash).
So, I’m doing a little playing/investigating…
If anyone knows, it would help.
Are there any ‘special’/custom settings/options or is the Qt in DS a ‘plain vanilla’ build?
What is the exact version of Qt in 18.104.22.168? (I’m thinking it’s 4.8.1..)
(Yes, I’m thinking of compiling my own Qt libs from source to see if I can pin it down any further than I have.)
Also, from trollling around the Valintina Db documentation, I came across a possible solution for the slow switches and what not with the various content ‘options’. A simple change to the CMS’s ini file pretty much solved the problem for me. All that needs to be changed is is the value for CacheSize (under Vkernel), by default it is 10 MB. It can go as high as half your system RAM but the Valintina folks don’t recommend going THAT high. 32, 64 or 128 would be good values…with 64 probably being more than enough for most people. 32 wiuld probably work for most.
What this does is move the cache to RAM, which is much faster than swapping to disk…which a 10MB, even though my content database isn’t THAT big, was happening a bit when switching.