EMULAB Forum
clrmamepro [English] => clrmame Discussion => Topic started by: Terra_Cresta on 27 November 2010, 17:53
-
On initial application start-up and periodically during use the profiler takes an inordinate amount of time to complete the "looking for datfiles" process. Admittedly, I have quite a few datfiles but for the most part this seems to be cached and seems to complete quite quickly.
It was pretty slow pre 3.137 but I thought it was just due to the sheer number of datfiles present. 3.137 seems to *add* something which makes the process slower taking up to four minutes to complete the "looking for datfiles" bit.
Is it a case of - to quote Bruce Hornsby - "That's just the way it is"?
-
actually nothing changed for ages in the profiler. can you maybe send me your setup in a compressed form somehow?
maybe something changed on your system? a going nuts virusscanner? some self created settings files? will do some checks next week but would be great to have your config setup.
-
It's quick as always here....so....any chance to send me your setup?
-
Hang in there :) I'll post tomorrow morning GMT. It's a 264Mb RAR... just uploading to a file sharing host.
http://www.sendspace.com/file/ynhy3a
-
thanks....downloaded the archive and only decompressed the datfile and settings folder into a new instance of cmpro 3.137....started it and it took 4 seconds(!) to load 2638 datfiles and settings files...
....will do the same with your full archive later on.....but it seems to be your system at the moment....
-
and now to your full archive:
cmpro64.exe (3.137): 5 seconds
cmpro.exe (3.134b): 5 seconds
cmpro_3.89a: 2 min 1 second
cmpro_3.88: 1 min 59 seconds
well, as you can see it's fast enough for the current version...I think 5 seconds to process ~2600 dats and ~2600 settings files is ok.
There is no reason to keep such old (4.5 years!) cmpro versions like 3.89a or 3.88.
by the way, testing system was a 64bit Windows 7 on a C2D 6600 cpu with 4GB...and a fast HD....nothing really up2date l33t pc...
-
If it can help anyone AV software seemed to be the cause. Once the CMPro folder was excluded from scans profiler loads in just a few seconds. :)
Cheers Boss.
-
So....if you want to have a speedy profiler, add cmpro's settings and datfile folder to the virusscanner's exclusion list....they contain only text/xml files anyway....
-
I know this thread is old, but I'm having the same problem.
- It happens at the first opening AND after a looong time clrmamepro remained closed
- It opens instantly after I closed it
- I have a lot less DATs than TC (I'd attached the htm report.)
- I added the complete clrmamepro folder to avast IS exclusion list (I always used the EXE to install it and to update it)
Maybe a fragmented disk C is causing this? (I'm just guessing)
-
Turn off virusscanners completly (for a test) and be sure you didn't use 3rd party tools to mass-create cmpro profiles...
Last time I've checked it it loaded something >3000 profiles within seconds...
all I can say for now...