This is an automated email from the ASF dual-hosted git repository.
chhsiao pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/mesos.git
The following commit(s) were added to refs/heads/master by this push:
new afc53be Updated the 1.7.0 release blog post description to match the
figure.
afc53be is described below
commit afc53bed3a6a2ab31aff128ee0bf097d06f2d332
Author: Chun-Hung Hsiao <[email protected]>
AuthorDate: Tue Sep 25 13:24:16 2018 -0700
Updated the 1.7.0 release blog post description to match the figure.
Review: https://reviews.apache.org/r/68842
---
site/source/blog/2018-09-24-mesos-1-7-0-released.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/site/source/blog/2018-09-24-mesos-1-7-0-released.md
b/site/source/blog/2018-09-24-mesos-1-7-0-released.md
index 6c3cc16..577b253 100644
--- a/site/source/blog/2018-09-24-mesos-1-7-0-released.md
+++ b/site/source/blog/2018-09-24-mesos-1-7-0-released.md
@@ -19,7 +19,7 @@ In Mesos 1.7, we put a lot of emphasis on performance. Thanks
to the community
-* The master `/state` 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 `/state` endpoint are more responsive.
+* The master `/state` 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 `/state` endpoint are more responsive.
* [Mesos
containerizer](http://mesos.apache.org/documentation/latest/mesos-containerizer/)
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.
* The agent `/containers` 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.
* 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.
