Best practices
- Deploy with a figure you thought about, not a placeholder. Then correct it from the first recommendation. A generous placeholder is paid for every month until you act on the recommendation to lower it.
- Look into a quick memory stop before you accept. If a connector is stopped for memory minutes after it starts, check what is holding memory in your program first. More memory may only hide the cause.
- Choose the gap between your limit and your request on purpose. Every recommendation keeps it. A limit set at ten times the request will be offered again at ten times the new one.
- Take cost recommendations in a quiet window. The saving is real and so is the restart.
- Read the invoice direction before you accept. A recommendation that fixes a risk usually costs more. That is the trade being offered, not a mistake.
- Start a stopped connector before expecting advice about it. Nothing measured while it is stopped describes it doing its work.
Common pitfalls
Reading silence as a fault
A quiet Insights tab is normal. Check that the connector is being watched, and read When Insights has nothing to say, before raising a ticket.Waiting for Condense to resize the connector for you
It will not. If a reservation needs to change, somebody has to accept it. That is deliberate: the change costs a restart, and a restart is not something to do to your connector without asking.Accepting a cost recommendation without reading what else it changes
Lowering a reservation saves money, and it also means that when a node runs short, your connector is closer to the front of the queue to be stopped, because that queue is decided by how far usage sits above the reservation. The recommendation says so.Setting a limit at the highest value the form accepts and calling the connector protected
A memory limit no node could ever hand out can never be reached, so it can never contain anything.Related
Accept, dismiss or set your own
What you can do with a recommendation.
Glossary
The words used on these pages.