Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Fri, 6 Nov 2015 05:17:28 +0000 (UTC)
From: "Naganarasimha G R (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12741589.1410813850000.171321.1446787048240@Atlassian.JIRA>
In-Reply-To: <JIRA.12741589.1410813850000@Atlassian.JIRA>
References: <JIRA.12741589.1410813850000@Atlassian.JIRA>
 <JIRA.12741589.1410813850346@arcas>
Subject: [jira] [Commented] (YARN-2556) Tool to measure the performance of
 the timeline server
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Naganarasimha G R commented on YARN-2556:
-----------------------------------------

Hi [~sjlee0] & [~lichangleo]
In Some Forum User Query came across an issue where each Insert was taking more time when the existing Level DB data size was more(about 3GB disk size), continuously at the rate of 10 inserts per sec for span of 15 mins  . During each Insertion, query is happening to pick the Date for identifying {{CreationTime}} which i presume to be the reason for ATS inserts being slow. May be we can optimize the test to have some initial Level DB Data and then test the performance. This would also be useful to evaluate the performance of ATSV1.5. Thoughts ?


> Tool to measure the performance of the timeline server
> ------------------------------------------------------
>
>                 Key: YARN-2556
>                 URL: https://issues.apache.org/jira/browse/YARN-2556
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>            Reporter: Jonathan Eagles
>            Assignee: Chang Li
>              Labels: BB2015-05-TBR
>             Fix For: 2.8.0
>
>         Attachments: YARN-2556-WIP.patch, YARN-2556-WIP.patch, YARN-2556.1.patch, YARN-2556.10.patch, YARN-2556.11.patch, YARN-2556.12.patch, YARN-2556.13.patch, YARN-2556.13.whitespacefix.patch, YARN-2556.14.patch, YARN-2556.14.whitespacefix.patch, YARN-2556.15.patch, YARN-2556.2.patch, YARN-2556.3.patch, YARN-2556.4.patch, YARN-2556.5.patch, YARN-2556.6.patch, YARN-2556.7.patch, YARN-2556.8.patch, YARN-2556.9.patch, YARN-2556.patch, yarn2556.patch, yarn2556.patch, yarn2556_wip.patch
>
>
> We need to be able to understand the capacity model for the timeline server to give users the tools they need to deploy a timeline server with the correct capacity.
> I propose we create a mapreduce job that can measure timeline server write and read performance. Transactions per second, I/O for both read and write would be a good start.
> This could be done as an example or test job that could be tied into gridmix.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)