Author Topic: PAR2 multithreaded  (Read 5693 times)

Offline rmeijer

  • Contributor
  • ***
  • Posts: 4
PAR2 multithreaded
« on: April 29, 2010, 01:26:53 pm »
Problem: PAR2 uses 1 CPU-core for unparring (time to unpar = long)

What if you have 4 CPU-cores and use only 1 core for unparring..?
Use the multithreaded version of par2cmdline 0.4, a utility to create and repair data files using Reed Solomon coding. par2 parity archives are commonly used on Usenet postings to allow corrupted postings to be repaired instead of needing the original poster to repost the corrupted file(s).

This version has been modified to utilise the Intel Threading Building Blocks 2.2 library, which enables it to process files concurrently instead of the original version's serial processing. Computers with more than one CPU or core such as those using Intel Core Duo, Intel Core 2 Duo, or AMD Athlon X2 CPUs can now create or repair par2 archives much quicker than the original version. For example, dual core machines can achieve near-double performance when creating or repairing.

par2cmdline 0.4 also supports CUDA, which enables you to process data using the processor of your video card GPU (Nvidia Only!).

Alt.binz developers, wouldn't be nice if this tool could be added to alt.binz? Or create an addon for alt.binz with multithreaded par2 functionalities?

More info: http://chuchusoft.com/par2_tbb/index.html
Or a simular tool with an interface: http://www.ice-graphics.com/ICEECC/IndexE.html

Please your thoughts about this request.
« Last Edit: April 29, 2010, 01:39:06 pm by rmeijer »

Offline davidq666

  • Contributor
  • ***
  • Posts: 1302
  • Watashi Wa Ero Desu!
Re: PAR2 multithreaded
« Reply #1 on: April 29, 2010, 02:41:12 pm »
the new par2.exe is suposed to be multicore:

0.31.2
+ new faster multicore par2.exe inside altbinz

Offline Hecks

  • Contributor
  • ***
  • Posts: 2011
  • naughty cop
Re: PAR2 multithreaded
« Reply #2 on: April 29, 2010, 07:23:24 pm »
Methinks there is confusion here between par2 checking and repairing on the one hand, and unraring on the other.  The latter isn't multicore, AFAIK.