[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:
Depends
depends on SERVER-464 background index creation Closed
depends on SERVER-479 global read/write lock Closed
depends on SERVER-494 bulk delete concurrency - don't lock ... Closed
is depended on by SERVER-114 json + js in admin interface( was: XM... Closed
is depended on by SERVER-381 add option to db.eval not to lock Closed
is depended on by SERVER-302 Unable to connect to a pair during a ... Closed
is depended on by SERVER-305 ctrl-c in shell should terminate curr... Closed
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)

Generated at Thu Feb 08 02:53:43 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.