[
https://issues.apache.org/jira/browse/AURORA-471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14007838#comment-14007838
]
David McLaughlin commented on AURORA-471:
-----------------------------------------
Update: the thrift serialization is a red herring. I created a 2000 task job in
the IsolatedSchedulerModule with a production-like payload size and then ran
tests with Java profiling. The query takes around 60ms and Thrift serialization
takes 500ms - so the rest of the time *appears* to be spent in transport.
> 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
> Attachments: browser-profile.png, jobsummary-profile.png
>
>
> 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)
