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

Make thread control behaviour more intuitive #1039

Open
rambaut opened this issue Nov 13, 2018 · 1 comment
Open

Make thread control behaviour more intuitive #1039

rambaut opened this issue Nov 13, 2018 · 1 comment

Comments

@rambaut
Copy link
Contributor

rambaut commented Nov 13, 2018

BEAGLE 3's CPU kernel is multithreaded. The number of threads produced can be controlled on the command line using the -beagle_thread_count option. The previous -threads controls the number of BEAST threads. The -threads option should be come the priority controlling the overall number of threads.

If only -threads N is specified, given K partitions, then each partition's BEAGLE instance will be created with N/K threads (rounded down?).

If only -beagle_thread_count X is given then each BEAGLE instance has X threads.

If both -threads N and -beagle_thread_count X is specified then there are N threads in the BEAST thread pool and each BEAGLE instance has X threads.

@rambaut rambaut added this to the v1.10.5 milestone Nov 13, 2018
@rambaut
Copy link
Contributor Author

rambaut commented Nov 13, 2018

This just leaves what the default behaviour is. Currently this would result in BEAST using an auto-sizing thread pool with each BEAGLE instances left to create a default number of threads (currently 8?).

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

No branches or pull requests

1 participant