Subject: [mongodb-user] Churning lots of databases in test
We're running mongo 3.4 (wiredtiger) in our test environment, and as our company has grown, we have started churning lots of databases in our test environment. We create and drop several thousand databases per day, and have noticed that the database does not perform as well as it used to. I've noticed that when the virtual size grows larger than the amount of memory available, that performance tanks. Does anyone else have experience limiting the virtual size of the database, or dealing with a system that creates and drops thousands of databases? I'm mostly wondering if there is a more optimal way to do the cleanup. We first drop all of the collections, and then have a periodic cleanup job that does the actual drop in order to avoid the global lock, but am wondering if something can be done to improve this even more, and whether or not this is causing our performance issues.
You received this message because you are subscribed to the Google Groups "mongodb-user"
For other MongoDB technical support options, see: https://docs.mongodb.com/manual/support/
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]
To post to this group, send email to [email protected]
Visit this group at https://groups.google.com/group/mongodb-user
To view this discussion on the web visit
For more options, visit https://groups.google.com/d/optout