slower than actually running on database about mongodb-memory-server HOT 4 CLOSED

All 27 test cases (where 13 are using mongoose) take on my Mac only 11 seconds for graphql-compose-mongoose

What OS do you use?
Please provide output log for new MongoMemoryServer({ debug: true })
Thx.

from mongodb-memory-server.

This may actually be a mongoose issue for low performance on Windows, there has been an issue reporting low performance on mongoose.

gist including the output

Windows 10 Version 1803 (Build 17134.81)
mongoose v5.1.4
MongoDB v3.2.7

from mongodb-memory-server.

Spinning up a fresh database for every test file is slower than using with installed and running mongod process on dev machine.

BUT if you run tests in parallel (2-4 workers) with mongodb-memory-server you should get performance win in total execution time. With one process of mongod it quite complex task to prepare tests and code for parallel execution.

from mongodb-memory-server.

I don't think I am starting a fresh database for every test file, and I am not trying to achieve running tests in parallel right now (although that would be great to do), I actually initialize the database only once and run all tests in sequence.

Even after solving the mongoose performance issue, the result for mongodb-memory-server is still the same.

from mongodb-memory-server.