Mongodb compass UI unresponsive when a collection size is more than 30MB, and average size of document could more than 5MB.
Is there any reason why it is slow, or is there any limitations on collection or document sizes.
Skip to main content
The slowness of Compass will have more to do with where your server is running, the capacity of your and how you are connected to your server.
It will also depend on what else is running on the machine where Compass is running.
@Naveen_K2 can you share some more details about what’s slow?
There is a known issue about switching back and forth between JSON view and other views which we are planning to release a fix for soon.
Hi Marcon,
Our Mongodb server was located in USA, I was working from India. So, there is a collection which has more than 200md in size and the average doc size is 4mb. While I’m trying to view that collection through MongoDB Compass its taking a while to load and also some times the entrie screen going to blank(white screen) which show only top left 3 options(connect, view , help)
Server
and Compass
with
seem to confirm
2 years later
Hi
Sorry for the digging, couldn’t find a way to create a new one.
We have a similar problem, details below:
- Only two people are experiencing the UI getting unresponsive. Other 5 people are not facing this behavior
- It occurs even when people use the same connection string
- It only occurs in a specific collection
- It only occurs using MongoDB Compass. Using the web data explorer everything is fine
- We are all in Brazil
- The cluster is in Brazil region
- The collection has ~4,4M documents, with avg doc size 2,95 kB
- Restarting the computer or reinstalling MongoDB Compass from scratch doesn’t seem to work
- MongoDB Compass is in the latest version available
- The first 100 documents are loaded into screen but the entire UI gets unresponsive, while the document count is still running. The UI only allow the users to interact after the document count (around 30s after the interaction)
- Changing back to a tab where another collection is open is OK but going back is worse: the entire window gets unresponsive for a while
Again: we have only 2 from 7 people experiencing this. All computers have the same hardware and software, we are using windows
Any thoughts?
New & Unread Topics
| Topic | Replies | Views | Activity |
|---|---|---|---|
| data loss when doing mongorestore | 0 | 237 | Jul 2024 |
| MongoDB Compass 1.44 breaks SSH tunneling | 2 | 91 | Sep 2024 |
| C# aggregation with dynamic group stage based on params | 1 | 38 | Oct 2024 |
| What does the “isTruncated” field in the slow query logs mean? | 0 | 55 | Nov 2024 |
| How to remove stale/idle temporary or staging collections created by application | 0 | 63 | Dec 2024 |