[SERVER-21629] Improve performance with WT with more than 10K active tables Created: 23/Nov/15 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | 3.0.7 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Daniel Pasette (Inactive) | Assignee: | Backlog - Storage Engines Team |
| Resolution: | Unresolved | Votes: | 4 |
| Labels: | WTMultiTableCache | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Storage Engines
|
||||||||||||
| Sprint: | Storage 2017-01-23 | ||||||||||||
| Participants: | |||||||||||||
| Case: | (copied to CRM) | ||||||||||||
| Description |
|
This is a spinoff from Once there are more than 10K tables, I now see all the time being spent opening and closing sessions and cursors, because the caching layer bounds how many we keep open since 3.0.6. I can code around that, but then I'm not testing how the system actually behaves. |