Performance & Optimization

Showing 18 of 4010

Please add support for auto-incrementing numeric IDs. For example, if an ID starts at 1000001, the next created record should automatically use 1000002

What problem are you trying to solve? Focus on the what and why of the need you have, not the how you'd like it solved. MongoDB lacks native support for auto-incrementing numeric IDs, forcing applications to use custom counter logic, which in...

Altaab Ansari 19 days ago in Performance & Optimization / Querying & Aggregations 3 Future Consideration

1 VOTE

Generative AI and Smart Automation should be a key priority. MongoDB Atlas could significantly improve developer productivity by introducing AI-assisted query optimization that doesn’t just flag inefficient queries, but actively rewrites them into optimized alternatives. Automated index recommendations based on real workload telemetry would help teams make better performance decisions without deep manual analysis. Additionally, bot-assisted support workflows could speed up issue resolution by guiding users through diagnostics and common fixes more efficiently. Together, these capabilities would provide strong competitive differentiation while improving operational efficiency for both developers and platform teams.

What problem are you trying to solve? Focus on the what and why of the need you have, not the how you'd like it solved. Teams struggle to proactively identify and fix performance issues in MongoDB workloads. Query inefficiencies, missing or s...

Spideyyy N/A 18 days ago in Atlas Monitoring, Alerts & Observability / Data Modeling & Indexing / Performance & Optimization 1 Future Consideration

1 VOTE

Show latest document first instead of first document, in list

What problem are you trying to solve? Focus on the what and why of the need you have, not the how you'd like it solved. What would you like to see happen? Describe the desired outcome or enhancement. Why is this important to yo...

Profit Buddy AI 19 days ago in Performance & Optimization / Querying & Aggregations 1 Future Consideration

9 VOTE

Should be possible to configure profiling output destination

When enabling database profiling the output is sent to both the system.profile collection and system logs. Logging to a capped collection is fine but spamming the logs on disk is not good. We have a need to be able to react to changing query patt...

Guest over 2 years ago in Performance & Optimization 0 Submitted

3 VOTE

Allow the ability when NVME cluster to autoscale up based on CPU and Memory

To provide autoscaling capability for MongoDB NVME clusters based on CPU utilization and memory metrics. This feature would automatically provision additional resources when predefined thresholds are reached, ensuring optimal performance during us...

Guest 12 months ago in Performance & Optimization 0 Submitted

3 VOTE

Add support for all type of joins like Postgres has and improve performance

$lookup is a performance killer. Joins are crucial parts in every OLTP system. $lookup is the equivalent to join in SQL, however $lookup is slow, doesn't support hash joins or other efficient join algorithm implemented in Postgres for example. Se...

Guest about 1 year ago in Performance & Optimization 1 Submitted

6 VOTE

Implement $bucket and $group on indexed values with sub-linear runtime

We noticed that sum $bucket and $group aggregations such as $min, $max, $count are unexpectedly slow even when fully covered by an index, (partially) because the DB scans through the entire index rather than employing optimization approaches such ...

Guest about 3 years ago in Performance & Optimization 0 Submitted

1 VOTE

Provide a dictionary for matched/modified/deleted counts for bulk writes

Current bulk write operations provide only aggregated counts that look like this: ``` { acknowledged: true, insertedCount: 0, insertedIds: {}, matchedCount: 2, modifiedCount: 2, deletedCount: 0, upsertedCount: 0, upsertedIds: {} } ``` All ...

Guest 11 months ago in Performance & Optimization 0 Submitted

1 VOTE

Execute $group on shardPart instead of mergerPart

Basically what is described here: https://www.mongodb.com/community/forums/t/how-to-enforce-mongodb-to-execute-group-on-shardpart-of-the-execution-plan/267560 When running covered count queries that could be aggregated independently on the shards...

Guest about 1 year ago in Performance & Optimization 0 Submitted

1 VOTE

Parallelize unionWith

Today $unionWith aggregation command is executed sequentially. EG first we query collection A and then collection B and then the union occurs. The process should be parallelized so the query part will run in parallel while the union will be done a...

Guest over 1 year ago in Performance & Optimization 0 Submitted

Please enter your email address

FILTER BY CATEGORY