Tevtevd opened a new issue, #31300:
URL: https://github.com/apache/superset/issues/31300

   ### Bug description
   
   We've recently deployed SuperSet on Kubernetes and we've really struggling 
with performance
   
   A 26 row query using a Select * in SQL Lab takes 8-10 seconds, similar 
behavior in charts on any data source we use. Virtual or Direct. When running 
the same queries direct against the PostgresDB it takes around 1 second...
   
   We're having a really tough time overcoming this being new. Anyone who can 
help will be a life-saver. We're on latest version.
   
   ### Screenshots/recordings
   
   ![Screenshot 2024-12-05 
114200](https://github.com/user-attachments/assets/cfaa3972-c866-438b-8ce5-3dd090208965)
   ![Screenshot 2024-12-05 
114150](https://github.com/user-attachments/assets/d9bbf0d5-69d7-4fd7-a004-6122998a616b)
   
   
   ### Superset version
   
   4.1.1
   
   ### Python version
   
   3.11
   
   ### Node version
   
   18 or greater
   
   ### Browser
   
   Chrome
   
   ### Additional context
   
   _No response_
   
   ### Checklist
   
   - [X] I have searched Superset docs and Slack and didn't find a solution to 
my problem.
   - [X] I have searched the GitHub issue tracker and didn't find a similar bug 
report.
   - [X] I have checked Superset's logs for errors and if I found a relevant 
Python stacktrace, I included it here as text in the "additional context" 
section.


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