[jira] [Commented] (AURORA-471) Measure performance of the getTasks API call

["Bill Farner (JIRA)" <ji...@apache.org>]

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

Bill Farner commented on AURORA-471:
------------------------------------

If it's helpful, there's a stat on the server side for this.  Unfortunately it's not broken out into percentiles, but it might let you derive some information.

{noformat}
scheduler_thrift_getTasksStatus_events
scheduler_thrift_getTasksStatus_events_per_sec
scheduler_thrift_getTasksStatus_nanos_per_event
scheduler_thrift_getTasksStatus_nanos_total
scheduler_thrift_getTasksStatus_nanos_total_per_sec
{noformat}

> Measure performance of the getTasks API call
> --------------------------------------------
>
>                 Key: AURORA-471
>                 URL: https://issues.apache.org/jira/browse/AURORA-471
>             Project: Aurora
>          Issue Type: Sub-task
>          Components: Scheduler, UI
>            Reporter: David McLaughlin
>            Assignee: David McLaughlin
>
> We are trying to improve the performance of the job page in the new UI. Preliminary profiling shows that most of the time is spent on the thrift.js call to getTasks. Before suggesting API improvements, we need to determine where time is being spent in the request. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)