This is an automated email from the ASF dual-hosted git repository.

git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/mesos-site.git


The following commit(s) were added to refs/heads/asf-site by this push:
     new 5a0dd0c  Updated the website built from mesos SHA: afc53be.
5a0dd0c is described below

commit 5a0dd0ca7c9eaa440a2a9a35887db2092f99e51d
Author: jenkins <[email protected]>
AuthorDate: Tue Sep 25 22:44:41 2018 +0000

    Updated the website built from mesos SHA: afc53be.
---
 content/blog/feed.xml                        | 2 +-
 content/blog/mesos-1-7-0-released/index.html | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/content/blog/feed.xml b/content/blog/feed.xml
index 6618076..276fde1 100644
--- a/content/blog/feed.xml
+++ b/content/blog/feed.xml
@@ -27,7 +27,7 @@
 &lt;p&gt;&lt;img src=&quot;/assets/img/blog/mesos-1-7-0-performance.png&quot; 
alt=&quot;Mesos 1.7 performance improvements&quot; /&gt;&lt;/p&gt;
 
 &lt;ul&gt;
-&lt;li&gt;The master &lt;code&gt;/state&lt;/code&gt; endpoint is now more than 
twice as fast as before, and its processing is parallelized to provide higher 
throughput. As a result, Mesos UI and all tooling that consumes the 
&lt;code&gt;/state&lt;/code&gt; endpoint are more responsive.&lt;/li&gt;
+&lt;li&gt;The master &lt;code&gt;/state&lt;/code&gt; endpoint is now about 
twice as fast as before, and its processing is parallelized to provide higher 
throughput. As a result, Mesos UI and all tooling that consumes the 
&lt;code&gt;/state&lt;/code&gt; endpoint are more responsive.&lt;/li&gt;
 &lt;li&gt;&lt;a 
href=&quot;http://mesos.apache.org/documentation/latest/mesos-containerizer/&quot;&gt;Mesos
 containerizer&lt;/a&gt; has been a high-performance alternative to the Docker 
runtime, and now it’s even faster: launch and destroy throughput has increased 
by 2x in this release.&lt;/li&gt;
 &lt;li&gt;The agent &lt;code&gt;/containers&lt;/code&gt; endpoint no longer 
leads to high CPU consumption and thus is much more responsive. It now scales 
well to hundreds of containers running on the agent.&lt;/li&gt;
 &lt;li&gt;We made several optimizations to the resource allocator so the 
allocation cycle is now 20% faster on a 1,000-node cluster, and more 
significant improvements in this area are in progress for the 1.8 
release.&lt;/li&gt;
diff --git a/content/blog/mesos-1-7-0-released/index.html 
b/content/blog/mesos-1-7-0-released/index.html
index 72ca939..f99d475 100644
--- a/content/blog/mesos-1-7-0-released/index.html
+++ b/content/blog/mesos-1-7-0-released/index.html
@@ -147,7 +147,7 @@
 <p><img src="/assets/img/blog/mesos-1-7-0-performance.png" alt="Mesos 1.7 
performance improvements" /></p>
 
 <ul>
-<li>The master <code>/state</code> endpoint is now more than twice as fast as 
before, and its processing is parallelized to provide higher throughput. As a 
result, Mesos UI and all tooling that consumes the <code>/state</code> endpoint 
are more responsive.</li>
+<li>The master <code>/state</code> endpoint is now about twice as fast as 
before, and its processing is parallelized to provide higher throughput. As a 
result, Mesos UI and all tooling that consumes the <code>/state</code> endpoint 
are more responsive.</li>
 <li><a 
href="http://mesos.apache.org/documentation/latest/mesos-containerizer/";>Mesos 
containerizer</a> has been a high-performance alternative to the Docker 
runtime, and now it’s even faster: launch and destroy throughput has increased 
by 2x in this release.</li>
 <li>The agent <code>/containers</code> endpoint no longer leads to high CPU 
consumption and thus is much more responsive. It now scales well to hundreds of 
containers running on the agent.</li>
 <li>We made several optimizations to the resource allocator so the allocation 
cycle is now 20% faster on a 1,000-node cluster, and more significant 
improvements in this area are in progress for the 1.8 release.</li>

Reply via email to