[SERVER-19029] Configure boost thread to more closely model the standard Created: 18/Jun/15 Updated: 05/Feb/16 Resolved: 18/Jun/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code, Performance |
| Affects Version/s: | None |
| Fix Version/s: | 3.1.5 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Andrew Morrow (Inactive) | Assignee: | Andrew Morrow (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Platform 5 06/26/16 |
| Participants: |
| Description |
|
Currently, we build boost thread with interruption points enabled, which slows some concurrency primitives. We also build it to deal with broken libc that returns EAGAIN from pthread_mutex_lock. We don't believe we have any platforms where that occurs, because SimpleMutex doesn't special case that outcome. We should apply the BOOST defines that disable interruption and assume a conforming pthread_mutex_ subsystem. |
| Comments |
| Comment by Githook User [ 18/Jun/15 ] |
|
Author: {u'username': u'acmorrow', u'name': u'Andrew Morrow', u'email': u'acm@mongodb.com'}Message: |