From notifications-return-53084-archive-asf-public=cust-asf.ponee.io@superset.apache.org Tue Sep 29 03:08:46 2020 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mxout1-he-de.apache.org (mxout1-he-de.apache.org [95.216.194.37]) by mx-eu-01.ponee.io (Postfix) with ESMTPS id 46FA7180642 for ; Tue, 29 Sep 2020 05:08:46 +0200 (CEST) Received: from mail.apache.org (mailroute1-lw-us.apache.org [207.244.88.153]) by mxout1-he-de.apache.org (ASF Mail Server at mxout1-he-de.apache.org) with SMTP id B5C976415B for ; Tue, 29 Sep 2020 03:08:45 +0000 (UTC) Received: (qmail 28498 invoked by uid 500); 29 Sep 2020 03:08:44 -0000 Mailing-List: contact notifications-help@superset.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@superset.apache.org Delivered-To: mailing list notifications@superset.apache.org Received: (qmail 28488 invoked by uid 99); 29 Sep 2020 03:08:44 -0000 Received: from ec2-52-202-80-70.compute-1.amazonaws.com (HELO gitbox.apache.org) (52.202.80.70) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Sep 2020 03:08:44 +0000 From: =?utf-8?q?GitBox?= To: notifications@superset.apache.org Subject: =?utf-8?q?=5BGitHub=5D_=5Bincubator-superset=5D_zuzana-vej_commented_on_issu?= =?utf-8?q?e_=2310969=3A_Is_there_any_other_way_to_accelerate_dashboard=3F?= Message-ID: <160134892396.32230.16234418803554254513.asfpy@gitbox.apache.org> Date: Tue, 29 Sep 2020 03:08:43 -0000 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit In-Reply-To: References: zuzana-vej commented on issue #10969: URL: https://github.com/apache/incubator-superset/issues/10969#issuecomment-700398686 @appleyuchi the 3 major ways to optimize dashboard (excluding possibility with some issue with configurations which I wouldn't know about): 1. Engine optimization - can you use faster engine (as @nytai pointed out above) 2. Query optimization -- how complex is the SQL of your queries for the dashboard charts? Are you doing multiple joins, calculations, etc. did you limit how much data you query, optimizing the SQL query should have impact on the load time of your dashboard. 3. Dashboard complexity -- how complex is your dashboard meaning how many total charts do you have on the dashboard? These an initial load time to process metadata of the charts. We have seen in some cases for dashboards with large number of charts, and large amount of metadata (filter scopes, color settings etc) that just this time can go up to 7 seconds. By large number of charts I mean scale of 200 charts on a dashboard. There is `logs` table which you can go through to understand little more on where the time is coming from. It should have details on slice_id so you can see which charts are slowest, and the json column I believe should have lot more details. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: users@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org For additional commands, e-mail: notifications-help@superset.apache.org