#46 Set the threadcount to zero to automatically use the maximum system resources

[Nathan Tenney]

The multithreading code has some problems (see ticket:88 and ticket:179) that must be fixed before this can be done.

[David P. Chassin]

• status changed from new to closed
• resolution set to postponed

[Matthew Hauer]

• status changed from closed to reopened
• type changed from defect to task
• resolution postponed deleted

This mostly asks, 'are we comfortable with the multithreading implimentation as it is now?'
The specific thing to change in the trunk is at core/globals.h:71.

[Matthew Hauer]

• status changed from reopened to assigned
• version changed from 2.0 to 3.0
• milestone set to Version 3.0 RC 1

[David P. Chassin]

• description modified (diff)

The default threadcount should not be made 0 (use max) until the following conditions are satisfied.

1. The validation code must produce the same outcomes for single and multithreaded runs.

2. The multithreaded runs must generally be faster, at least for larger models.

3. Multithreading must be work consistently on all supported platforms.

At the present time it satisfies none of these of conditions in trunk.

[David P. Chassin]

• version changed from 3.0 to trunk

[David P. Chassin]

This cannot be done until all multithreading is done using MTI and all modules properly lock data access.

[David P. Chassin]

• milestone changed from Version 3.0 RC 1 to Unscheduled