[SERVER-20167] Avoid spinlock in TimerStats Created: 27/Aug/15 Updated: 19/Sep/15 Resolved: 27/Aug/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Concurrency |
| Affects Version/s: | None |
| Fix Version/s: | 3.1.8 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Bruce Lucas (Inactive) | Assignee: | Martin Bligh |
| 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 | ||||||||
| Sprint: | QuInt 8 08/28/15 | ||||||||
| Participants: | |||||||||
| Description |
|
As we saw in
I haven't been able to demonstrate a performance issue for this because this stat is only update for write concern with w>1 or j:true, and both of those have other performance issues that dominate at the moment. Independent of that however, it seems like a good idea to forestall performance pitfalls for future uses of this class. |
| Comments |
| Comment by Githook User [ 31/Aug/15 ] |
|
Author: {u'username': u'martinbligh', u'name': u'Martin Bligh', u'email': u'mbligh@mongodb.com'}Message: |
| Comment by Githook User [ 31/Aug/15 ] |
|
Author: {u'username': u'martinbligh', u'name': u'Martin Bligh', u'email': u'mbligh@mongodb.com'}Message: |
| Comment by Githook User [ 31/Aug/15 ] |
|
Author: {u'username': u'martinbligh', u'name': u'Martin Bligh', u'email': u'mbligh@mongodb.com'}Message: |
| Comment by Githook User [ 31/Aug/15 ] |
|
Author: {u'username': u'martinbligh', u'name': u'Martin Bligh', u'email': u'mbligh@mongodb.com'}Message: |
| Comment by Martin Bligh [ 28/Aug/15 ] |
|
Don't think so, this one is speculative from code inspection. I'll do the network stats one though |
| Comment by Githook User [ 27/Aug/15 ] |
|
Author: {u'username': u'martinbligh', u'name': u'Martin Bligh', u'email': u'mbligh@mongodb.com'}Message: |