[SERVER-323] improved concurrency: read/write lock - yielding ops Created: 30/Sep/09 Updated: 12/Jul/16 Resolved: 09/Mar/10 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Performance |
| Affects Version/s: | None |
| Fix Version/s: | 1.3.4 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Eliot Horowitz (Inactive) | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Done | Votes: | 22 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 14/Jan/10 ] |
|
we're changing concurrency strategy a bit - going well so far |
| Comment by Dwight Merriman [ 30/Dec/09 ] |
|
if we can get yield() into update and remove (increasing concurrency that way), i think we should then push this back a ways for other work. |
| Comment by Mathias Stearn [ 17/Nov/09 ] |
|
Not sure if this should be a sub-issue, but ideally index creation shouldn't block reads. (concern from IRC discussion) |