You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
@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.
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.
The text was updated successfully, but these errors were encountered: