Tevtevd commented on issue #31300: URL: https://github.com/apache/superset/issues/31300#issuecomment-2520105219
> @Tevtevd Hello there! I'm here to help you with your SuperSet issue. I can assist you in solving bugs, answering questions, and becoming a contributor while you wait for a human maintainer. > > To address the performance issues you're experiencing with Apache Superset on Kubernetes, here are a few areas to investigate and optimize: > > 1. **Database Connection and Query Execution**: Ensure that the connection to your PostgreSQL database is optimized. Superset uses the `psycopg2` driver by default, and any connection issues or misconfigurations can lead to delays. Check for any connection errors or warnings in the Superset logs [[1]](https://github.com/apache/superset/blob/master/superset/db_engine_specs/postgres.py). > 2. **Caching**: By default, Superset's caching might be disabled. Enabling and configuring a caching layer, such as Redis, can significantly improve performance by reducing the load on your database and speeding up query results retrieval. Adjust the `CACHE_CONFIG` settings in your `superset_config.py` to use a cache backend like Redis [[2]](https://github.com/apache/superset/blob/master/superset/config.py)[[3]](https://github.com/apache/superset/blob/master/docs/docs/configuration/cache.mdx). > 3. **Superset Configuration**: Review the `SUPERSET_WEBSERVER_TIMEOUT` and other timeout settings to ensure they are appropriate for your environment. Increasing these values might help if your queries are taking longer to process [[2]](https://github.com/apache/superset/blob/master/superset/config.py). > 4. **Kubernetes Resource Allocation**: Ensure that your Kubernetes deployment has sufficient resources allocated. This includes CPU and memory for the Superset pods, as well as any database and caching services. Insufficient resources can lead to performance bottlenecks. > 5. **Network Latency**: Check for any network latency issues between your Superset deployment and the PostgreSQL database. This can be a common issue in cloud environments where services are distributed across different regions or zones. > 6. **Superset Version and Dependencies**: Make sure you are using compatible versions of Python, Node, and other dependencies as specified in the Superset documentation. Any mismatches can lead to unexpected performance issues. > > By addressing these areas, you should be able to improve the performance of your Superset deployment on Kubernetes. > > _To continue talking to [Dosu](https://dosu.dev), mention @dosu._ Thanks we've tried all of these things except for point 5 - Which we dont think is the issue currently as we do allot of data movement from our Clusters for other Products and theyre all built in same way. -- 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]
