This is an automated email from the ASF dual-hosted git repository.
bridgetb pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/drill-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 7f2595c edit cgroups doc
7f2595c is described below
commit 7f2595c99e44d017d506f04c1d0d3f545ecce06f
Author: Bridget Bevens <[email protected]>
AuthorDate: Wed Feb 6 15:24:04 2019 -0800
edit cgroups doc
---
docs/configuring-cgroups-to-control-cpu-usage/index.html | 16 ++++++----------
feed.xml | 4 ++--
2 files changed, 8 insertions(+), 12 deletions(-)
diff --git a/docs/configuring-cgroups-to-control-cpu-usage/index.html
b/docs/configuring-cgroups-to-control-cpu-usage/index.html
index e05950b..6b5d6e4 100644
--- a/docs/configuring-cgroups-to-control-cpu-usage/index.html
+++ b/docs/configuring-cgroups-to-control-cpu-usage/index.html
@@ -1295,7 +1295,7 @@
</div>
- Feb 5, 2019
+ Feb 6, 2019
<link href="/css/docpage.css" rel="stylesheet" type="text/css">
@@ -1351,16 +1351,16 @@ If you have Drill 1.13 running on the node, or you have
Drill 1.14 running on th
<p>You can set the CPU limit as a soft or hard limit, or both. You set the
limits with parameters in the <code>/etc/cgconfig.conf</code> file. The hard
limit takes precedence over the soft limit. When Drill hits the hard limit,
in-progress queries may not complete. Review the following sections that
describe the soft and hard limit parameters and then configure CPU limits. </p>
<p><strong>Soft Limit Parameter</strong><br>
-You set the soft limit with the <code>cpu.shares</code> parameter. When you
set a soft limit, Drill can exceed the CPU allocated if extra CPU is available
for use on the system. Drill can continue to use CPU until there is contention
with other processes over the CPU or Drill hits the hard limit. </p>
+You set the soft limit with the <code>cpu.shares</code> parameter. This
parameter takes an integer value, which specifies a relative share of CPU time
available to the tasks in a cgroup. For example, if there are two tasks and
cpu.shares is set to 100, each task receives half of the CPU time. The value
must be 2 or greater.When you set a soft limit, Drill can exceed the CPU
allocated if extra CPU is available for use on the system. Drill can continue
to use CPU until there is contention [...]
<p><strong>Hard Limit Parameters</strong><br>
-You set the hard limit with the <code>cpu.cfs_period_us</code> and
<code>cpu.cfs_quota_us</code> parameters. The <code>cpu.cfs_period_us</code>
and <code>cpu.cfs_quota_us</code> parameters set a hard limit on the amount of
CPU time that the Drill process can use. </p>
+You set the hard limit on the amount of CPU time that the Drill process can
use through the <code>cpu.cfs_period_us</code> and
<code>cpu.cfs_quota_us</code> parameters. </p>
<ul>
<li><p><strong><code>cpu.cfs_period_us</code></strong><br>
-The <code>cpu.cfs_quota_us</code> parameter specifies a segment of time (in
microseconds represented by <code>us</code> for µs) for how often the access to
CPU resources should be reallocated. For example, if tasks in a cgroup can
access a single CPU for 0.2 seconds out of every 1 second, set cpu.cfs_quota_us
to 200000 and cpu.cfs_period_us to 1000000. The upper limit of the
<code>cpu.cfs_quota_us</code> parameter is 1 second and the lower limit is 1000
microseconds. </p></li>
+Specifies a period in microseconds (represented by <code>us</code> for µs) to
indicate how often a cgroup's access to CPU resources should be
reallocated. For example, if you want tasks in a cgroup to have access to a
single CPU for 0.2 seconds in a 1 second window, set
<code>cpu.cfs_quota_us</code> to 200000 and <code>cpu.cfs_period_us</code> to
1000000. The upper limit of the <code>cpu.cfs_quota_us</code> parameter is 1
second and the lower limit is 1000 microseconds. </p></li>
<li><p><strong><code>cpu.cfs_quota_us</code></strong><br>
-The <code>cpu.cfs_quota_us</code> parameter specifies the total amount of
runtime (in microseconds represented by <code>us</code> for µs) for which all
tasks in the Drill cgroup can run during one period (as defined by
cpu.cfs_period_us). As soon as tasks in the Drill cgroup use the time specified
by the quota, they are throttled for the remainder of the time specified by the
period and not allowed to run until the next period. For example, if tasks in
the Drill cgroup can access a singl [...]
+Specifies the total amount of runtime in microseconds (represented by
<code>us</code> for µs), for which all tasks in the Drill cgroup can run during
one period (as defined by <code>cpu.cfs_period_us</code>). When tasks in the
Drill cgroup use up all the time specified by the quota, the tasks are
throttled for the remainder of the time specified by the period and they cannot
run until the next period. For example, if tasks in the Drill cgroup can access
a single CPU for 0.2 seconds out o [...]
</ul>
<h3 id="configuring-cpu-limits">Configuring CPU Limits</h3>
@@ -1398,11 +1398,7 @@ The <code>cpu.cfs_quota_us</code> parameter specifies
the total amount of runtim
</code></pre></div>
<hr>
-<p>For additional information, refer to the following documentation:<br>
-- <a
href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html";>https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html</a><br>
-- <a
href="resource_management_guide/sect-cpu-example_usage">resource_management_guide/sect-cpu-example_usage</a><br>
-- <a
href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html";>https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html</a>
-- <a
href="resource_management_guide/sec-cpu_and_memory-use_case">resource_management_guide/sec-cpu_and_memory-use_case</a></p>
+<p>For additional information, refer to the <a
href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/resource_management_guide/sec-cpu";>RedHat
documentation</a>. </p>
diff --git a/feed.xml b/feed.xml
index 3e396c5..9d9063f 100644
--- a/feed.xml
+++ b/feed.xml
@@ -6,8 +6,8 @@
</description>
<link>/</link>
<atom:link href="/feed.xml" rel="self" type="application/rss+xml"/>
- <pubDate>Mon, 04 Feb 2019 18:20:14 -0800</pubDate>
- <lastBuildDate>Mon, 04 Feb 2019 18:20:14 -0800</lastBuildDate>
+ <pubDate>Wed, 06 Feb 2019 15:20:29 -0800</pubDate>
+ <lastBuildDate>Wed, 06 Feb 2019 15:20:29 -0800</lastBuildDate>
<generator>Jekyll v2.5.2</generator>
<item>
