Open animesh opened 1 month ago
Hi @animesh that speed is pretty typical for larger datasets such as yours (I'm assuming this is proteomics data?). Unfortunately for single files, I have limited ability to implement multithreading; currently I implemented multithreading in a way where multiple files will be converted at once but each file can only be accessed by a single thread. This helps with larger datasets containing multiple files, but not for single file conversion. At this point, if you do not already have one, upgrading to faster storage would be the best solution as the speed ultimate depends on HDD/SSD read/write speeds.
As for the --chunk_size parameter, this affects how many scans are read into memory for conversion at once. If the value is large enough, it essentially just reads in all the scans in the current file. So the maximum --chunk_size is essentially the number of scans in the raw data.
yes @gtluu it is proteome of HeLa cell 👍🏽 SSD is not making much difference it seems but somehow fragpipe seems to convert much faster, roughly about in 20 minutes? i am guessing there code is not open source though?
This may be a limitation due to the fact that TIMSCONVERT is written in Python. Other platforms such as ProteoWizard MSConvert are written in C++, and while I'm not overly familiar with FragPipe, I believe it is written in Java. I would imagine the speed difference is due to these other software using compiled languages. You can find the source code for FragPipe here. I am not fluent in Java or C++ so I can't directly compare the differences in our implementation, but I am continuing performance improvements where I can within the capabilities of Python when possible.
I am trying to convert some HeLa sample generated raw data and on an average it takes about couple of hours, for example
is this normal? If so, is there way to speed up? I have tried several values for --chunk_size but that doesn't make much difference >10e6? Folder size is about 2G