Mailing-List: contact issues-help@mesos.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@mesos.apache.org
Date: Tue, 4 Apr 2017 18:49:42 +0000 (UTC)
From: "Michael Park (JIRA)" <jira@apache.org>
To: issues@mesos.apache.org
Message-ID: <JIRA.12923618.1450744136000.203583.1491331782184@Atlassian.JIRA>
In-Reply-To: <JIRA.12923618.1450744136000@Atlassian.JIRA>
References: <JIRA.12923618.1450744136000@Atlassian.JIRA> <JIRA.12923618.1450744136087@jira-lw-us.apache.org>
Subject: [jira] [Comment Edited] (MESOS-4235) JSON generation performance
 improvement
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 04 Apr 2017 18:49:46 -0000


    [ https://issues.apache.org/jira/browse/MESOS-4235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15955612#comment-15955612 ] 

Michael Park edited comment on MESOS-4235 at 4/4/17 6:49 PM:
-------------------------------------------------------------

There are still follow-up work to be done in regards to migrating rest of the endpoints, but the scope of this ticket has been met. Refer to MESOS-4732


was (Author: mcypark):
There are still follow-up work to be done in regards to migrating rest of the endpoints, but the scope of this ticket has been met.

> JSON generation performance improvement
> ---------------------------------------
>
>                 Key: MESOS-4235
>                 URL: https://issues.apache.org/jira/browse/MESOS-4235
>             Project: Mesos
>          Issue Type: Epic
>          Components: libprocess, master, stout
>            Reporter: Michael Park
>            Assignee: Michael Park
>              Labels: mesosphere, scalability, twitter
>             Fix For: 1.3.0
>
>
> This is an epic which evolved from MESOS-2353. As mentioned in the description of MESOS-2353, most of the work is spent performing memory allocation/deallocation. Some preliminary efforts have been made such as calling {{reserve}} for {{JSON::Array}}. There are still plenty of dynamic allocations being made especially from instances of {{JSON::Object}} which hold a {{std::map}} as a member.
> The current approach being adopted is to introduce a {{jsonify}} function which by-passes these unnecessary dynamic allocations and copying, and to simply hold references to the underlying objects.
> We plan to first introduce the {{jsonify}} function to {{stout}}, and update master's {{state}} endpoint, then proceed to update the rest of the system.


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)