You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@aurora.apache.org by "Zameer Manji (JIRA)" <ji...@apache.org> on 2014/09/11 20:41:33 UTC

[jira] [Commented] (AURORA-700) Scheduler UI should use asynchronous HTTP requests

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

Zameer Manji commented on AURORA-700:
-------------------------------------

[~davmclau]: Is this related to how thrift.js works or how we are using it?

> Scheduler UI should use asynchronous HTTP requests
> --------------------------------------------------
>
>                 Key: AURORA-700
>                 URL: https://issues.apache.org/jira/browse/AURORA-700
>             Project: Aurora
>          Issue Type: Task
>          Components: Scheduler
>            Reporter: David McLaughlin
>
> Currently the scheduler UI code was written to assume synchronous network requests - every API call blocks JS execution. This is really going to limit how many API calls we can make per controller before performance is noticeably degraded. Especially with features like the new update API and the pending reasons API call. 



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