[SERVER-16050] Frequent yielding/sleeping causes bad perf in collscan Created: 10/Nov/14 Updated: 03/Dec/14 Resolved: 10/Nov/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Concurrency |
| Affects Version/s: | None |
| Fix Version/s: | 2.8.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Geert Bosch | Assignee: | Geert Bosch |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Description |
|
Just querying for {x:1}in a database with a few thousand small records is 55% slower due to yielding after every 128 documents scanned. Part of the slowness is due to yielding after read doing a sleep. |
| Comments |
| Comment by Geert Bosch [ 10/Nov/14 ] |
|
This makes yielding locks more efficient. |
| Comment by Githook User [ 10/Nov/14 ] |
|
Author: {u'username': u'GeertBosch', u'name': u'Geert Bosch', u'email': u'geert@mongodb.com'}Message: Sleeping should not be necessary as ordering is purely determined |