Prachil-MI commented on issue #30402:
URL: https://github.com/apache/superset/issues/30402#issuecomment-2416005754

   Thank you @rusackas for your reply and help. Here are the answers for the 
questions that you asked - 
   
   > Does it work when you don't get tricky with it like that? 
   
   It does not. We have at least 5 dashboards and at most 16 dashboards on 
single component / page. Rest of the contents are static. When we do not apply 
the optimisation, whenever the first dashboard appears in viewport, all 
dashboards start loading simultaneously. At the same time, for each dashboard, 
the assets like JS and CSS starts loading and the overall loading process 
becomes so slow that one dashboard takes 15-20+ seconds to load. Once the first 
dashboard is loaded, rest of the dashboard takes 4-8 seconds to load. 
   
   > Does the dashboard itself behave as expected in Superset itself (non 
embedded)? 
   
   No. It loads in couple of seconds. 
   
   > This also looks like what happens when the DB is being the bottleneck, but 
if you're messing with the dashboard rendering process, I'd suspect that first.
   
   The database does not have more than 1000 rows on most of the dashboards. We 
reviewed everything with database and applied the necessary optimisations ever 
though the data was very small. We ensured that every query execution takes 
less than 60ms. 
   
   > Also, make sure your Angular app isn't doing something strange like 
re-rendeing the iframe repeatedly on scroll or some other event. 
   
   Checked this behaviour as well. It does not load the specific dashboard 
repeatedly. 
   
   **Additional Information**
   
   1. Most of the dashboards have one chart in them. 
   2. The issue still exists and appears randomly with any dashboard. 
   3. The issue does not appear on Safari, but a different one. In Safari, the 
data fails to load with http code 400. However, if the user refreshes the 
dashboard using the manual refresh button, the dashboard loads correctly. 
   
   


-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to