Helmut
My feedback
3 results found
-
14 votesHelmut
supported this idea
·
An error occurred while saving the comment -
37 votes
An error occurred while saving the comment Helmut
commented
Hi, especially for staging purpose it would be very important for us to have a single node option. The Shared options seem not to fit our purpose as even in Staging systems we have a lot of data (to detect performance impacts early). We see folks are questioning our costs on MongoDB Atlas for Staging. So having the single node option would helps us on various aspects (development, quality, business).
Cheers, HelmutHelmut
supported this idea
·
-
4 votesHelmut
supported this idea
·
This is a big cost topic!
We pay money for nothing to cloud providers.
Basically the current way of releasing storage in order reduce costs is highly manual and therefore not efficient.
Current process:
1. Identify releasable storage (we build now something on our own)
2. Run the compact on secondaries first and then finally switch primary.
Btw, the same happens on TTL indexes when they are first applied.
Why not...
* ...provide alerts if releasable storage is above a certain threshold?
* ...provide functionality to compact
* ... reduce the storages accordingly
Partly it might be possible via AppServices.