Docs Menu
Docs Home
/
MongoDB Atlas
/ / /

Review Drop Index Recommendations

On this page

  • Unused Indexes
  • Redundant Indexes
  • Hidden Indexes
  • Drop or Hide an Index

The Performance Advisor suggests dropping unused, redundant, and hidden indexes to improve write performance and increase storage space.

Tip

See also:

To learn more about the impact of unnecessary indexes, see Remove Unnecessary Indexes.

An index is unused if it doesn't support any queries.

The Performance Advisor flags an index as unused if it hasn't supported a query in 7 or more days after it was created or the server was restarted.

Note

The Performance Advisor inspects only the 20 most active collections for unused indexes.

An index is redundant if another index supports any query that it could.

The Performance Advisor flags an index as redundant if it matches the prefix of another index in the same collection.

Example

If a collection contains the indexes:

  • { a: 1 }

  • { b: -1 }

  • { a: 1, b: -1 }

{ a: 1 } is redundant because it matches the prefix { a: 1, b: -1 }.

{ b: -1 } is not redundant because it does not match any prefix.

In the Performance Advisor, redundant indexes are marked with a red Redundant badge. Below each redundant index, the Performance Advisor displays the related indexes that cover it.

Note

Related indexes are displayed for you to verify that the redundant index can be dropped safely. Related indexes are not recommended for removal.

Atlas doesn't use hidden indexes to support queries. They still impact write performance and consume storage space. To learn more, see Hidden Indexes.

You can hide an index to evaluate the impact of dropping an index before you drop it. Unhiding an index also takes less time than rebuilding a dropped index. To hide and unhide an index by using the Atlas UI, see Create, View, Drop, and Hide Indexes.

The Performance Advisor always recommends dropping hidden indexes. If you determine that a hidden index is unnecessary, drop it.

Note

The Atlas Performance Advisor page displays hidden indexes from your top 20 most active namespaces at the time you load the page. If you have more than 20 namespaces, the Performance Advisor page might not display all of your namespaces with hidden indexes.

Note

Consider hiding indexes before you drop them. Atlas supports hidden indexes for MongoDB version 5.0 and higher.

To drop or hide an index by using the Performance Advisor:

1
  1. If it's not already displayed, select the organization that contains your desired project from the Organizations menu in the navigation bar.

  2. If it's not already displayed, select your desired project from the Projects menu in the navigation bar.

  3. If it's not already displayed, click Clusters in the sidebar.

    The Clusters page displays.

2

If the replica set is part of a sharded cluster, first click the sharded cluster containing the replica set.

3
4

In the Performance Advisor tab, click Explore Recommendations on the Drop Indexes card.

5

By default, the results correspond to one of the primary hosts. However, you can select another host from the drop-down.

6

The Performance Advisor displays a dialog box with a link to the Atlas UI and a copyable MongoDB Shell command to drop that index.

The dialog box also provides a copyable MongoDB Shell command to hide that index.

7

To drop or hide an index by using the Atlas UI, click the Indexes tab, then click the Drop Index or Hide Index icon next to the index. Atlas displays a dialog box to confirm your selection. For more information, see Create, View, Drop, and Hide Indexes.

To drop or hide an index by using the MongoDB Shell, paste and run the command provided by the Performance Advisor.

Back

Index Ranking