Repository: mesos Updated Branches: refs/heads/master b863f6c78 -> 77279f025
Reformat email address in blog to avoid un-necessary updates to website. Email in "<[email protected]>" format in a markdown file causes random characters to be generated in the resulting html file causing the website bot generating a new commit everytime even though nothing changed. The fix here is to remove the angular brackets. Project: http://git-wip-us.apache.org/repos/asf/mesos/repo Commit: http://git-wip-us.apache.org/repos/asf/mesos/commit/77279f02 Tree: http://git-wip-us.apache.org/repos/asf/mesos/tree/77279f02 Diff: http://git-wip-us.apache.org/repos/asf/mesos/diff/77279f02 Branch: refs/heads/master Commit: 77279f0256d12edc8208dfd96a88fea205bde8a4 Parents: b863f6c Author: Vinod Kone <[email protected]> Authored: Thu May 10 13:07:11 2018 -0700 Committer: Vinod Kone <[email protected]> Committed: Thu May 10 13:10:08 2018 -0700 ---------------------------------------------------------------------- .../blog/2017-12-07-performance-working-group-progress-report.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/mesos/blob/77279f02/site/source/blog/2017-12-07-performance-working-group-progress-report.md ---------------------------------------------------------------------- diff --git a/site/source/blog/2017-12-07-performance-working-group-progress-report.md b/site/source/blog/2017-12-07-performance-working-group-progress-report.md index 0f59515..e641d25 100644 --- a/site/source/blog/2017-12-07-performance-working-group-progress-report.md +++ b/site/source/blog/2017-12-07-performance-working-group-progress-report.md @@ -87,4 +87,4 @@ We're currently targeting the following areas for improvements: * **[Libprocess](https://github.com/apache/mesos/tree/master/3rdparty/libprocess) HTTP performance**: This will be undertaken as part of improving the v1 API performance, since it is HTTP-based. * **Master state API performance**: Currently, API queries of the master's state are serviced by the same master actor that processes all of the messages from schedulers and agents. Since the query processing can block the master from processing other events, users need to be careful not to query the master excessively. In practice, the master gets queried quite heavily due to the presence of several tools that rely on the master's state (e.g. DNS tooling, UIs, CLIs, etc) and so this is a critical problem for users. This effort will leverage the state streaming API to stream the state to a different actor that can serve the state API requests. This will ensure that expensive state queries do not affect the master's ability to process events. -If you are a user and would like to suggest some areas for performance improvement, please let us know by emailing <[email protected]>. +If you are a user and would like to suggest some areas for performance improvement, please let us know by emailing `[email protected]`.
