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

Not really a realistic scenario, since I don't know anyone who does a) a full rebuild and having b) compress: rezip and sha1:both enabled. Such options are timekillers (beside the amout of a rebuild).
As an example, if you don't use rezip, sha1 none and hardlinks, your full rebuild is most likely done within an hour (depending a bit from where to where you operate)
I know the argument "but I want to be 100% sure that the archives are fine"...but actually a post run commandline based archive test is faster. Same can apply for "but I want identically compressed archives".
The typical use case for the rebuilder is to update an existing collection with a bunch of sets.

But of course, if you like to spend 4.25 hours to always redo everything, ok...it's of course doable ;-)

This time for version 254 and archives in zips so test differs from previous but I think most people will rebuild from zip files so it's more realistic scenario.

No caching taking place, rest assured, multiple runs take consistently around 500-510s with reboots in between
It should be noted that it's a powerful machine (12 core/24 thread, 64GB RAM, different SSD's for rebuilder source and target), but still the same I was using with rebuilder v0.05
The easy consideration would be that the new rebuilder scales linearly to the number of threads, but I suspect the relative performances of the source and target SSDs may play a role as well
Regardless, it's a huge improvement - at least for me

….and now compare it to old cmpro :-)

You have to be careful when comparing results...the diskcache can fool you immensly. So you need to compare either both with or without diskcache...
So the best ist (besides using the same source/destination) a reboot of the machine in between the tests and doing 1 scan.
Or you run multiple ones in a row for one version and take an average.

I'd expect something about 1 to 30% speed gain compared to 0.05...but yes, it also depends on your machine/number of cores

Server down error, I'm waiting for an update.

Hmmmmm "a nice speed boost" you say? Man I've just got a 234% speed increase!!!
I've reprocessed my latest full update job, and it took far less than half the time it took with rebuilder v0.05 (510s vs. 1194s. 42% of the time)
Whatever magic you've applied to Rebuilder v0.06, that's the way to go!!! 

Thank you Roman, will test its performance ASAP

Unrelated: should the rebuilder deserve its own thread now? I do understand it's the "next cmp" so to speak, but still...

Rebuilder 0.06 released

https://mamedev.emulab.it/clrmamepro/binaries/rebuilder_v006.zip
https://mamedev.emulab.it/clrmamepro/binaries/readme.html

Doing source and destination matches now in multiple threads...gives a nice speed boost.

Hi folks. How are we all doing? I am hoping somebody can give me some guidance on how to use clrmamepro properly to update my roms? I have MAME version 0.140 complete (as far as I know) without icons and artwork and samples I think but I do have the roms and CHD'S) I have always struggled to figure out how to update my collecton properly because the tutorials on the website are a bit sketchy to say the least.

Hi there! I understand that you're looking for some guidance on how to properly use clrmamepro to update your roms for MAME. It can definitely be a bit confusing to navigate, especially with unclear tutorials. Have you tried looking for any other resources online, or reaching out to any MAME or clrmamepro communities for help? It might also be helpful to break down the specific issues or questions you're running into, so that someone can provide more targeted guidance.

To read an XML file, you can use a text editor or an XML parser. Here are some steps you can follow to read a .xml file:

Open a text editor like Notepad, Sublime Text, or Visual Studio Code.

Go to "File" and select "Open". Navigate to the location of the .xml file you want to read and select it.

The .xml file will open in the text editor, displaying the XML code. You can then read the contents of the file and make any necessary changes.
This code will parse the XML file and print out the tag names and attributes of each element in the file. You can modify the code to access specific elements or attributes based on your needs.

It's important to note that while a text editor can display the contents of an XML file, it may not be the best tool for parsing and processing the file data. For more complex XML files, an XML parser is recommended.

Here are some steps you can follow to use an XML parser to read an XML file:

Choose an XML parser that fits your programming language and platform. Some popular options include:
Python: ElementTree, lxml, xml.etree.ElementTree
Java: SAX, DOM, JDOM, StAX
C#: XmlReader, XmlDocument, XDocument
Open the XML file in the parser by specifying the file path.

Parse the XML data using the parser's methods and functions. This can involve accessing specific elements or attributes, iterating through the entire file, or performing other operations on the data.

Once you have processed the data, you can output it to a file, database, or other destination as needed.

By using an XML parser, you can more easily and efficiently read and process the data contained in an XML file, making it a powerful tool for working with structured data.