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

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

21

clrmame Discussion / Re: CHD deep-scanning with recent CLR builds

« on: 23 October 2011, 21:04 »

Sure, Roman - I'd like to test out a single-threaded build when it's convenient for you to make one.  I'm curious to know if that's the issue. 

In case it helps, I'm running CMP 4.01 on Win7 x64 with a Sandy Bridge mobile proc (i7-2620M).  I also have an older C2D system I could try it on (as I understand it, threading models are completely different with the C2D architecture).

By the way, did CMP always have multi-threaded hash calculation?  If not, I could also try downloading/testing an old build that doesn't.  Also, are there any other features in CMP that are multi-threaded?

Thanks again, Roman.

22

clrmame Discussion / Re: CHD deep-scanning with recent CLR builds

« on: 23 October 2011, 15:11 »

Ok, benchmarks:

CHD deep scan area51.chd (CMP 4.01): 10mins 55secs
chdman -verify area51.chd: 2mins 54secs

So yes, considerable difference there, assuming those two operations are equivalent in function (both decompressing and checking CHD against hashes).  Again, based on what you said earlier I'm now thinking CMP 3.x builds could exhibit the same behavior, though I haven't tested with any of those lately (though I could if you think it would help). 

Either way this is odd CMP behavior considering it uses the same code as chdman as you mentioned.

23

clrmame Discussion / Re: CHD deep-scanning with recent CLR builds

« on: 22 October 2011, 15:16 »

Thanks for the info, Roman - even if it wasn't the greatest news at least I understand a little more what's actually happening.  By the way, it sounds like you are referring to general incompatibilities with CMP and SAMBA, not just CHD deep scanning, right?  I didn't notice any issues with SAMBA other than this performance issue, and scanning was pretty quick without the "deep" option flagged, though now that I think about it, I haven't rebuilt anything with that setup either.

Anyway, it seems there are only a few options to attempt resolving the performance problem:

1) Attach the ext4 drive to a Win7 system and use something like this to read it.

2) Use CMP with Wine on a Linux system with the ext4 drive attached (any issues that you know of there?)

3) Wait for CMP to become a little more Linux fs friendly (and not I'm not about to bug you about that, but wait I just did, ooh see what I did there?) 

Thoughts? 

24

clrmame Discussion / Re: CHD deep-scanning with recent CLR builds

« on: 21 October 2011, 22:58 »

Wow, not sure what's wrong here then.  Are you aware of any performance differences between deep scanning to a remote WinXP/NTFS drive vs. Linux/ext4 over SAMBA?  It's the only other thing I can think of, since I think I was using the former when I noticed faster results. 

25

clrmame Discussion / Re: CHD deep-scanning with recent CLR builds

« on: 21 October 2011, 12:11 »

Thanks, Roman.  Would be great to know what you find.

26

clrmame Discussion / CHD deep-scanning with recent CLR builds

« on: 14 October 2011, 22:46 »

Recently I've observed that with the 4.x versions of CLR, deep-scanning CHDs (i.e. with "Decompress CHD and check MD5/SHA-1" option flagged) takes longer than I recall with the 3.x versions - perhaps even twice as long.  Is this a known issue with recent builds or could this be on my end?  I don't have any other "Hash and CHD" tab options flagged but maybe there's something else to tune for better performance?  Thanks.