forked from cloudfoundry/docs-cf-admin
-
Notifications
You must be signed in to change notification settings - Fork 2
/
max-container-starts.html.md.erb
16 lines (12 loc) · 962 Bytes
/
max-container-starts.html.md.erb
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
---
title: Setting a Maximum Number of Started Containers
owner: Diego
---
<strong><%= modified_date %></strong>
This topics describes how to use the auctioneer job to configure the maximum number of app instances running at a given time. This prevents Diego from scheduling too much work for your platform to handle. A lower default can prevent server overload, which may be important if you're using a small server.
The auctioneer only schedules a fixed number of app instances to start at one time. This limit applies to both single and multiple Diego Cells. For example, if you set the limit to five started instances, it does not matter if you have one Diego Cell with ten instances or five Diego Cells with two instances each. The auctioneer will not allow more than five instances to start at the same time.
<% if vars.product_name == "CF" %>
<%= partial "max-container-starts" %>
<% else %>
<%= partial "../opsguide/max-container-starts" %>
<% end %>