Isnt better to use maximum cores rather than only one ? Its better do things faster. Users dont know how many cores have 
Cpu cores - utilization
Well so I thought, but in the case of Retrieiving Acoustic Ids this seemed to cause problems in some cases.
- Not sure if the genpuid code can always handle multiple concurrent usage, although not confirmed I think it can cause occasional crashes on Macs.
- Although you may have multiple CPU’s you only have one I/O channel and so if reading from multiple files concurrently can just create too much file contention.
With Windows 7 64Bit I never had any problems to use 4 cores with Jaikoz/Genpuid or MusicIP-Mixer/Genpuid. For me it was just 4 times faster than with 1 core
I’m also using Windows 7 x64 and if my CPU gadget is to be believed, when using Jaikoz, then all four CPUs are being used.
TenBaz
Most critical parts of Jaikoz such as Correct From Musicbrainz have been written multi-threaded so Jaikoz does indeed take advantage of of multiple cpus.
If you run the ‘Retrieve Acoustic Ids’ task then Jaikoz uses some code that I didn’t write (genpuid.exe & mipcore.exe) and by default we only run one instance of these at a time because they seem to crash occasiioanlly when run in parallel. But you can change these to use multiple cpus as well by changing the setting in Preferences/Musicbrainz/MusicIP/Maximum Cpus to use when Retrieve Acoustic Ids.
I have problems with puid generation. Before 3.8 was everything ok, multiple core generation was ok. Now im using 2 cores and must run multiple times. Maybe puids are generated but not sended to AF, because they are checked like “wait 24hrs”
Hmm nothings was changed for puid generation except for adding the option to allow you to specify how many cpus to use. Probably best to email me your support files with some more details.
New fingerprints are always sent to MuscIP, however I don’t think that the process of allocating puids for these fingerprints is fully automated, so the 24 hrs is a guide rather than definite fact.
So I think unfortunately the problem lies with AmpliFIND, I will contact them.
I got the crash in 4. beta.
I hate windows and had to set cpu usage to 1 in ctrl+alt+del proces jaikoz. Now it continued on the fly. I started today with my 50000+ music collection screwed over by Itunes earlier, any suggestions on how to do this? Preferences?
Please respond.
Sorry do what exactly ?
Well I’m asking how to optimize the best way with only 1 core @ 1,73 ghz going to process all the 50000 tracks. So how do I get all the cores working or should I just wait a week to finish it on half speed?
If its crashing using multiple cores, you can either:
-
Restart it when it crashes, as long as using defaults Jaikoz saves the acoustic id to the file as its generated so it will just skip over the files that have already been done.
-
Reduce cpus to one, then wait longer.
-
Use another tool to generate the puids, You can use Genpuid directly to generate puids and this can work on follders and hopefully use multiple cpus using just one instance. But it doesnt put the puids into the file itself so it would have to be used with a script.
Right, so far I figured it out, I hope it will be checked in the next release. What I figured so far is that I work about 20 tracks a minute… so reasonable speed (I like my 120Mb connection). The I/O outbound should be channeled as a fallback release. If it is possible in the architecture: one plugin (genpuid) first during identification and the other afterwards (changes kept by log). Anyway, is some nice Ubuntu support coming up? I bet there is some community behind development there.
After a little discovering I found out that A: going to Ubuntu helps. B: raising java memory helps C: diminishing the amount of objects helps D: Checking the use 1 core in Am… menu helps.
Thanks for this fantastic program (under Ubuntu at least : 4.0.0 Beta 3)
Kind Regards,
Hans