[ https://issues.apache.org/jira/browse/CLOUDSTACK-9783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15885599#comment-15885599 ]
ASF GitHub Bot commented on CLOUDSTACK-9783: -------------------------------------------- Github user rhtyd commented on the issue: https://github.com/apache/cloudstack/pull/1944 @borisstoyanov can you see the failure in Travis with test_list_infrastructure_metrics test case? Thanks @rashmidixit you're right I added this as a plugin to keep it separate from the core APIs. If this is a major concern, I can move these APIs to server/api modules. From the UI, to remove this service they can modify the core metrics widget to do no-operation (in ui/scripts/ui-custom/metricsView.js) and the rendered button can be modified to be hidden, alternatively metricsView section can be removed across the resources (zones, cluster, host, vms, volumes and storage pool). > Improve metrics view performance > -------------------------------- > > Key: CLOUDSTACK-9783 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9783 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Reporter: Rohit Yadav > Assignee: Rohit Yadav > Fix For: Future, 4.10.0.0, 4.9.3.0 > > > Metrics view is a pure frontend feature, where several API calls are made to > generate the metrics view tabular data. In very large environments, rendering > of these tables can take a lot of time, especially when there is high > latency. The improvement task is to reimplement this feature by moving the > logic to backend so metrics calculations happen at the backend and final > result can be served by a single API request. -- This message was sent by Atlassian JIRA (v6.3.15#6346)