I'm updating scilpy (This PR) and I try to understand how the multithreading works with commit and make sure that when I ask for a specific number of threads it does what it is suppose to do.
I'm testing everything using this quick nextflow pipeline. Here is the command line and script I used test_commit.tar.gz:
We are trying to understand the issue. I have some questions for you.
To properly interpret your reports, shall we read the values reported as "Run times" or "CPU-Hours"? They seem to go in opposite directions and I don't have experience with Nextflow reports. Sorry!
To understand where a possible bottleneck is, would it be possible to split the time profiling into two parts? Specifically, we would like to know the execution time (with different threads of course) only when running the function "tck2dictionary.run()" and when running the fit. That would help us a lot.
Hello COMMIT Team,
I'm updating scilpy (This PR) and I try to understand how the multithreading works with commit and make sure that when I ask for a specific number of threads it does what it is suppose to do.
I'm testing everything using this quick nextflow pipeline. Here is the command line and script I used test_commit.tar.gz:
Then I check the report.html
If you change nb_threads (4 or 8) the report is very confusing. check reports.tar.gz
I tried also to run directly the python script with this command line:
Still quite understand why It does not use all the processes I allow him to use.
Thank you in advance for your help Arnaud