MasMadd commented on issue #29636: URL: https://github.com/apache/superset/issues/29636#issuecomment-3068488132
> Still wondering if the 5.0 release, or anything thereafter, have improved the situation here. If you think you have some setup/steps we can follow for consistent benchmarking/reproduction, that could help. Otherwise, I could _suspect_ that the shared connection pool might be part of the issue (See [#31868](https://github.com/apache/superset/issues/31868), [#27897](https://github.com/apache/superset/issues/27897), for example), but I'm just not sure. > > CC [@betodealmeida](https://github.com/betodealmeida) [@mistercrunch](https://github.com/mistercrunch) All the information needed to reproduce the bug is in the post itself, unfortunately I don't know what else to provide :/. However, even with this lack of parallelization, I was able to at least reduce the truly long dashboard rendering times by decreasing query execution times, using ad-hoc indexes and materialized views on the database. Unfortunately, for now, I can't follow the advice to update the superset version; I'm currently using the one specified in the post itself and I'm not allowed to modify it in my project. -- 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]
