Hey! Thanks for the ping! I’ll try to answer your questions to the best of my ability. We use wired tiger in production and we have had reported data sizes of 11GB compress down to 2GB but we have also seen some numbers like 11GB down to 6GB. Still amazing but there is a pretty big difference in reports.
The time it takes to start your app could be a few things. It could be a slow internet or latency depending on where you are relative to where your mongodb is located.
Could you clarify on what you mean in terms of best practices? MMS has a lot of functionality and we’ve used it to trace observers, inefficient queries, we’ve seen the effects of both OPLOG tailing and long polling and the different issues that arise in either use case when we have high velocity data (eg. 100k documents bulk inserted/updated) and how that effects our meteor servers.
If you have specific questions I would be happy to answer of if you have general ideas I can also try to assist to the best of my ability.
Let me know