Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multiple threads not working! #2

Open
jlehtoma opened this issue Apr 27, 2015 · 3 comments
Open

Multiple threads not working! #2

jlehtoma opened this issue Apr 27, 2015 · 3 comments
Labels
Milestone

Comments

@jlehtoma
Copy link
Member

Multiple threads (more than full hardware threads used by default) does not work currently. Consecutive runs using exactly the same setups produces different results. Until fixed, do not use --use-threads=N.

@jlehtoma jlehtoma added the bug label Apr 27, 2015
@jlehtoma jlehtoma added this to the 4.1 milestone Apr 27, 2015
@jlehtoma
Copy link
Member Author

Faulty behavior is confirmed using ESMK data both for CAZ and ABF. Additional analysis features (e.g. Info-Gap uncertainty) do not matter. So far tested with 1, 2, 8 and 34 threads on our server setup (Ubuntu 12.04 LTS x64). Except for --use-threads=1 the results for the same setup are different for consecutive runs. While using --use-threads=1 produces the same results when run consecutively, the results still differ from the default (no --use-threads defined). This is most probably a bug with delegating and/or aggregating the calculations of individual features.

@underbluewaters
Copy link

Is this still the case? I was seeing a 1.6x performance boost using 8 cores vs 1.

@jlehtoma
Copy link
Member Author

@underbluewaters AFAIK, this is still the case. There may be a performance boost, but there is no guarantee that the results are correct.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants