[
https://issues.apache.org/jira/browse/MESOS-2353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14382920#comment-14382920
]
Benjamin Mahler edited comment on MESOS-2353 at 3/26/15 11:23 PM:
------------------------------------------------------------------
EDIT: That master failed over.. :)
On a small staging cluster, these changes seem to have helped ~ 45%:
{noformat:title=before}
$ /usr/bin/time curl -s master:5050/state.json > /dev/null
0.17 real 0.00 user 0.00 sys
{noformat}
{noformat:title=after}
$ /usr/bin/time curl -s master:5050/state.json > /dev/null
0.10 real 0.00 user 0.00 sys
{noformat}
Will report back when I know how it behaves on large clusters.
was (Author: bmahler):
On a small staging cluster, these changes seem to have helped ~ 7.5x:
{noformat:title=before}
$ /usr/bin/time curl -s master:5050/state.json > /dev/null
0.17 real 0.00 user 0.00 sys
{noformat}
{noformat:title=after}
$ /usr/bin/time curl -s master:5050/state.json > /dev/null
0.02 real 0.00 user 0.00 sys
{noformat}
Will report back when I know how it behaves on large clusters.
> Improve performance of the master's state.json endpoint for large clusters.
> ---------------------------------------------------------------------------
>
> Key: MESOS-2353
> URL: https://issues.apache.org/jira/browse/MESOS-2353
> Project: Mesos
> Issue Type: Improvement
> Components: master
> Reporter: Benjamin Mahler
> Assignee: Benjamin Mahler
> Labels: newbie, scalability, twitter
>
> The master's state.json endpoint consistently takes a long time to compute
> the JSON result, for large clusters:
> {noformat}
> $ time curl -s -o /dev/null localhost:5050/master/state.json
> Mon Jan 26 22:38:50 UTC 2015
> real 0m13.174s
> user 0m0.003s
> sys 0m0.022s
> {noformat}
> This can cause the master to get backlogged if there are many state.json
> requests in flight.
> Looking at {{perf}} data, it seems most of the time is spent doing memory
> allocation / de-allocation. This ticket will try to capture any low hanging
> fruit to speed this up. Possibly we can leverage moves if they are not
> already being used by the compiler.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
