Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id E22B2200C38 for ; Wed, 1 Mar 2017 06:43:53 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id E0C2C160B7E; Wed, 1 Mar 2017 05:43:53 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 360F6160B7C for ; Wed, 1 Mar 2017 06:43:53 +0100 (CET) Received: (qmail 59364 invoked by uid 500); 1 Mar 2017 05:43:52 -0000 Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list issues@cloudstack.apache.org Received: (qmail 59355 invoked by uid 500); 1 Mar 2017 05:43:52 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 59352 invoked by uid 99); 1 Mar 2017 05:43:52 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Mar 2017 05:43:52 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id E1A6318E122 for ; Wed, 1 Mar 2017 05:43:51 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -2.347 X-Spam-Level: X-Spam-Status: No, score=-2.347 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-2.999, SPF_NEUTRAL=0.652] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id TafI8I3NwvNZ for ; Wed, 1 Mar 2017 05:43:48 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 466AC5FB43 for ; Wed, 1 Mar 2017 05:43:47 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 58256E053A for ; Wed, 1 Mar 2017 05:43:46 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 4621224158 for ; Wed, 1 Mar 2017 05:43:45 +0000 (UTC) Date: Wed, 1 Mar 2017 05:43:45 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CLOUDSTACK-9783) Improve metrics view performance MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 01 Mar 2017 05:43:54 -0000 [ https://issues.apache.org/jira/browse/CLOUDSTACK-9783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15889539#comment-15889539 ] ASF GitHub Bot commented on CLOUDSTACK-9783: -------------------------------------------- GitHub user rhtyd reopened a pull request: https://github.com/apache/cloudstack/pull/1944 CLOUDSTACK-9783: Improve metrics view performance This improves the metrics view feature by improving the rendering performance of metrics view tables, by re-implementing the logic at the backend and data served via APIs. In large environments, the older implementation would make several API calls that increases both network and database load. List of APIs introduced for improving the performance that re-implement the frontend logic at backend: listClustersMetrics listHostsMetrics listInfrastructure listStoragePoolsMetrics listVMsMetrics listVolumesMetrics listZonesMetrics Pinging for review - @abhinandanprateek @DaanHoogland @borisstoyanov @karuturi @rashmidixit Marvin test results: === TestName: test_list_clusters_metrics | Status : SUCCESS === === TestName: test_list_hosts_metrics | Status : SUCCESS === === TestName: test_list_infrastructure_metrics | Status : SUCCESS === === TestName: test_list_pstorage_metrics | Status : SUCCESS === === TestName: test_list_vms_metrics | Status : SUCCESS === === TestName: test_list_volumes_metrics | Status : SUCCESS === === TestName: test_list_zones_metrics | Status : SUCCESS === You can merge this pull request into a Git repository by running: $ git pull https://github.com/shapeblue/cloudstack 4.9-metrics-enhancement Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cloudstack/pull/1944.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1944 ---- commit 402253504e9520104caf9fbc1317042f2fd89474 Author: Rohit Yadav Date: 2017-02-16T08:15:15Z CLOUDSTACK-9783: Improve metrics view performance This improves the metrics view feature by improving the rendering performance of metrics view tables, by reimplementing the logic at the backend and data served via APIs. In large environments, the older implementation would make several API calls that increases both network and database load. List of APIs introduced for improving the performance: listClustersMetrics listHostsMetrics listInfrastructure listStoragePoolsMetrics listVMsMetrics listVolumesMetrics listZonesMetrics Signed-off-by: Rohit Yadav ---- > 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)