[ https://issues.apache.org/jira/browse/YARN-2556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
chang li updated YARN-2556: --------------------------- Attachment: yarn2556_wip.patch Thanks [~airbots] for the substantial early work! I have moved the test job into mapreduce jobclient tests to avoid circular dependency. I have tested the patch, and it has successfully shown the write time, write counters and write per second. I will continue to work on it to add more metric of measurement such as transaction rates, IO rates and memory usage. > 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 > Attachments: YARN-2556-WIP.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)