It works better now. I was previously storing whole blobs to the MongoDB rather that changing subsets of the documents using $set. This cause my oplog to grow out of control, which in turn seemed to affect the querying in MongoDB compass. After my changes to how I store data, the initial load of the 20 posts takes only 3-5 down from ~30 seconds.
However, I still feel like this is a bit annoying. Is there anyway I can “choose what the default query is”, clicking a collection in the menu to the left in Compass? The way Compass deals with the load of the collection is locking any user iteraction out until loaded. This is very frustrating and becomes a bottleneck when I try to interact with the database.
Compass: Version 1.19.12
MongoDB Atlas: M10
Store a few hundred blobs of data un-indexed and without using $set (so that oplog takes a hit). Open compass, click collection, wait until it loads.
One big difference having 5 second load time and 30, is that I’m running on a paid tier. That could be the main difference now from then. However 30 seconds is ALOT and also being locked out from user interaction in Compass as it loads is another problem.