Choose what your connector reserves

Four fields set how much CPU and memory your connector reserves and how much it may use. All four are required, and they are the only fields Insights ever recommends changing, so a few minutes spent on them when you deploy pays back every month. A request is what your connector reserves. It is what work is placed by and what your invoice is calculated from, whether or not the connector uses it. A limit is the cap on what your connector may use.

​

Requests for CPU

Reserves CPU for each copy of your connector.

• Too low: the node is over-committed, and your connector and its neighbours slow down under load.
• Too high: reserved CPU sits idle, and nodes stay on that could have been switched off.
• Highest it accepts: 2000 m.

​

Limits for CPU

Caps how much CPU each copy may use.

• Too low: your connector is held back and runs slower than the node could let it run.
• Too high: one spike can crowd out everything else on the same node.
• Highest it accepts: 2000 m.

​

Requests for RAM

Reserves memory for each copy.

• Too low: a full node still looks as though it has room, so work lands there and slows down.
• Too high: memory nothing uses is still reserved, and still charged.
• Highest it accepts: 8000 Mib.

​

Limits for RAM

Caps how much memory each copy may use before it is stopped.

• Too low: your connector is stopped for passing its cap while it still had work to do.
• Too high: nothing contains a climb in memory, and the node stops other workloads to survive.
• Highest it accepts: 8000 Mib.

A request cannot be larger than its own limit, so a request above its matching limit is refused wherever you enter it.

​

If you do not know the figures yet

That is the normal starting point. Enter something sensible and let the first recommendation correct it. That is what Insights is for. You can:

• Enter your own figures for all four fields.
• Leave the defaults and correct them later from a recommendation.

​

How many copies run

The same section has Autoscaling Parameters, where you set the range of replicas Condense may run, for example 2 to 6. Condense moves the number of copies up and down inside that range without asking you. It is a separate decision from the four figures above: replicas change how many copies there are, the figures change how big each copy is.

​

Next steps