[SERVER-85055] Tracking: M1 Performance improvement ideas Created: 07/Jul/23  Updated: 13/Jan/24  Resolved: 03/Oct/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Charlie Swanson Assignee: Backlog - Query Integration
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-76597 Reported size of TelemetryMetrics is ... Closed
depends on SERVER-77267 Investigate if using std::shared_ptr<... Closed
depends on SERVER-76042 Avoid re-parsing match, sort and proj... Closed
depends on SERVER-78783 Reduce contention by including thread... Closed
depends on SERVER-80242 Investivate wildcard index read perfo... Closed
depends on SERVER-80941 Speed improvements for shapifying Mat... Closed
depends on SERVER-75272 Improve performance of checking if te... Closed
depends on SERVER-77485 Avoid re-constructing an ExpressionCo... Closed
depends on SERVER-77567 Cap memory size of query stats store ... Closed
depends on SERVER-78003 Avoid dynamic_cast in $not serialization Closed
depends on SERVER-78677 Change SerializationOptions to a cons... Closed
depends on SERVER-79736 Hash C++ data structures directly rat... Closed
depends on SERVER-81065 Cache the hash of the client metadata... Closed
is depended on by SERVER-85107 Tracking: Performance is "good enough" Closed
Related
related to SERVER-85064 Tracking: M0 performance improvement ... Closed
Assigned Teams:
Query Integration
Participants:

 Description   

This ticket is just a placeholder to link all the things we need to do before accepting performance.


Generated at Thu Feb 08 06:56:42 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.