[SERVER-29088] Cache uuid in Collection class to fix perf regression Created: 05/May/17 Updated: 30/Oct/23 Resolved: 08/May/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 3.5.7 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Geert Bosch | Assignee: | Geert Bosch |
| Resolution: | Fixed | 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 | ||||
| Steps To Reproduce: | Micro-benchmarks doing simple inserts. |
||||
| Sprint: | Storage 2017-05-29 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
Getting CollectionOptions from a CatalogEntry actually requires lookups in the catalog table, making retrieving UUIDs for collections costly, while it was expected to be near free. Instead cache the UUID directly inside the Collection class. |
| Comments |
| Comment by Githook User [ 08/May/17 ] |
|
Author: {u'username': u'GeertBosch', u'name': u'Geert Bosch', u'email': u'geert@mongodb.com'}Message: |