Ticket #5909 (closed: fixed)
Allow the number of OpenMP threads to be set a little more freely
| Reported by: | Martyn Gigg | Owned by: | Martyn Gigg |
|---|---|---|---|
| Priority: | major | Milestone: | Release 2.3 |
| Component: | Mantid | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: | Tester: | Russell Taylor |
Description
Currently, Algorithm::execute sets the number of OpenMP threads to be used to the config value when an algorithm starts. It would be useful and not difficult to allow the number of threads to be set at runtime from python. This would allow different parts of a script to use different numbers of threads (mostly useful for debugging probably)
Change History
comment:2 Changed 8 years ago by Martyn Gigg
Don't reset the num of threads for each algorithm... Refs #5909
instead set it once from the config value when the framework starts. Also exposed the setters to python to give greater control at runtime.
Changeset: 97fc4f16f5dfd9b8f757b5ab89285a37c556ff37
comment:3 Changed 8 years ago by Martyn Gigg
- Status changed from accepted to verify
- Resolution set to fixed
comment:4 Changed 8 years ago by Russell Taylor
- Status changed from verify to verifying
- Tester set to Russell Taylor
comment:5 Changed 8 years ago by Russell Taylor
- Status changed from verifying to closed
Works. A minor gripe is that if you don't have a config value set, there's no way to go back to the default number of threads other than by remembering what it was.
comment:6 Changed 8 years ago by Martyn Gigg
Don't reset the num of threads for each algorithm... Refs #5909
instead set it once from the config value when the framework starts. Also exposed the setters to python to give greater control at runtime.
Changeset: 97fc4f16f5dfd9b8f757b5ab89285a37c556ff37
