ThermoRawFileParser icon indicating copy to clipboard operation
ThermoRawFileParser copied to clipboard

Convert using a configurable number of cores

Open azzamallow opened this issue 6 years ago • 3 comments

When I run ThermoRawFileParser I notice it uses 2 cores (I think) while doing the conversion. I have a large machine that has many cores, and id like to use a configurable number of cores for the conversion.

To make use of all the cores on my machine I have written a script which executes many ThermoRawFileParser processes in parallel, so I have a solution to my problem. However, specifying the number of cores to use would make it easier for me to make full use of my machine and not require such a script.

azzamallow avatar Dec 04 '18 03:12 azzamallow

Hi,

Thanks for your input. Do you mean providing a list of RAW files as an argument to the parser or processing a single RAW file in a multi-threaded way?

I know the Thermo library API has some multi-threaded methods but I didn't get around to using it in my code.

Best regards,

Niels

nielshulstaert avatar Dec 07 '18 13:12 nielshulstaert

@nielshulstaert In this respect. We have done some performance comparisons with the previous proteowizard conversion and the previous Thermo Windows API was 6 times faster than our library. I will make this data available soon.

ypriverol avatar Dec 07 '18 13:12 ypriverol

Sorry for the late response, I mean processing a single RAW file in a multi-threaded way.

Cheers.

Aaron

Hi,

Thanks for your input. Do you mean providing a list of RAW files as an argument to the parser or processing a single RAW file in a multi-threaded way?

I know the Thermo library API has some multi-threaded methods but I didn't get around to using it in my code.

Best regards,

Niels

azzamallow avatar Dec 13 '18 02:12 azzamallow