Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[GDT]

Today I upgraded to te latest 4.046b, coming from 4.045 and started to mantain my romsets with MAME .247 release. I got very slow speed with scanning (with fix) or rebuilding. What happened?
The archive is on a SATA 7200RPM disk (170mb/sec speed with cleardiskmark).

Thank you.

[Roman]

How should I know what happened ;-)

There were no changes from 4.045 to 4.046b which were anyhow speed related. And since noone else reported such a slow down, it must be something on your end.....could be anything...from a busy hd (due to other threads accessing it, incl. virusscanners), to bad network drivers when it's a net drive, etc...etc.

Or maybe you've enabled things like sha1 checking or other time consuming options.

So...."What happened" is nothing I can give an answer to.

"Here it runs fine and fast"

[GDT]

I didn't make any change in settings (SHA1, etc.) other romsets seems to be almost unchanged in terms of speed.
Disk isn't busy and tried to reboot the whole PC.
The antonpisa snaps archive is a quite large zip file (almost 1.8 GB) so I supposed that something was changed with the newer version, but if it isn't so I'll have to make some further checks.

[Roman]

Ah....you're scanning snaps....sorry...didn't see that (even when it's listed as the topic ;-))

Turn off fix missing....and usually it's better to keep them decompressed.

The reason is that progettosnaps usually add placeholder dummy pics for a couple (and that can be hundreds) of sets which cmpro can detect and add. But this "look into the current zip, find the file, add it" (and that some hundred times) can really slow down the process. So...turn off "fix missing". Usually adding the missing ones with the rebuilder is faster.

[yescabernetnointernet]

How should I know what happened ;-)

There were no changes from 4.045 to 4.046b which were anyhow speed related. And since noone else reported such a slow down, it must be something on your end.....could be anything...from a busy hd (due to other threads accessing it, incl. virusscanners), to bad network drivers when it's a net drive, etc...etc.

Or maybe you've enabled things like sha1 checking or other time consuming options.

So...."What happened" is nothing I can give an answer to.

"Here it runs fine and fast"

Dont'k know how to debug, but in WINE latest clrmamepro runs slow also.
(Yeah, could be something "wrong" on WINE side)
I'm using it on Windows, at the moment.

[Roman]

again...define "runs slow"...where? What do you do? Scanning? Rebuilding? Which sets (e.g. snaps are something totally different than MAME sets), are they compressed or not etc..etc... WINE on its own is of course already a problem....but you can simply exchange cmpro with an older version to see if there's a difference. The changes from 4.045 to 4.046b are not scanner/rebuilder related, they only fix stuff in underlying structures

[yescabernetnointernet]

WINE on its own is of course already a problem....

Yup! 


it's slower everywhere.
On standard sets (rom+chd+sample) when Rebuilding / Scanning.
Also even when when selecting the radio button in "You Prefer" (both Rebuilder and Scanner):

• On Windows it changes the selection (almost) immediately.
• On WINE it takes several sesconds.

I'll give a shot with previous WINE version(s).

Roman, do you provide some place where I can download all the old releases of clrmamepro?

[Roman]

What do you expect when you run WINE ;-) Surely it's slower. clrmampro is a native windows program, no support for weird emulation bugs sorry ;-)

I don't keep older versions, however I bet you can find it somewhere....but still, there were no changes regarding speed and if it's already slow for you to toggle a radio button, it sounds more like a WINE issue.

[yescabernetnointernet]

What do you expect when you run WINE ;-) Surely it's slower. clrmampro is a native windows program, no support for weird emulation bugs sorry ;-)

You're right.
To be fair, some clrmamepro/WINE combos runs as fast as in Windows.
This wouldn't be an issue if every clrmamepro release had always been slower on every WINE version! 

P. S.: hey Roman, have you ever wondered releasing clrmamepro' sources to the public? 

[GDT]

I re-tried just now, previously I was fixing my MAME romset. I disabled fix missing but it's surely slower than before (it started 40 minutes ago and still running), with same hardware/set (mame snaps)/archive/settings... I use your great tool for almost 15 years... never got this issue.

edit: I leaved tha scan running and got back after 6 hours... well it was still running, so I killed the process...

How should I know what happened ;-)

There were no changes from 4.045 to 4.046b which were anyhow speed related. And since noone else reported such a slow down, it must be something on your end.....could be anything...from a busy hd (due to other threads accessing it, incl. virusscanners), to bad network drivers when it's a net drive, etc...etc.

Or maybe you've enabled things like sha1 checking or other time consuming options.

So...."What happened" is nothing I can give an answer to.

"Here it runs fine and fast"

Dont'k know how to debug, but in WINE latest clrmamepro runs slow also.
(Yeah, could be something "wrong" on WINE side)
I'm using it on Windows, at the moment.

[Roman]

The only time killers for snaps are: Fix Missing and maybe Scanner->Advanced->>Deeper check for fixable missing files.

If they are turned off scanning them should rather fast.
Of course it depends a bit how the snaps set is stored. Since it's one big set with thousands of pngs, any fixing operation is time intensive on it. Especially if you keep the files in a solid 7z archive for example. Then it's pretty normal that it takes hours if it has to fix lots of files (it would recompress the data over and over again).

You can try to use the rebuilder to add the update sets from progetto and then do a scan without any fix operations to see what's still wrong.....

...or think about storing them decompressed