Connection pooling - how many connections is Explo maintaining with my data source?

Last updated: April 7, 2025

Understanding Connection Pools

Our system uses a connection pool to manage database queries efficiently. By default, there are 9 concurrent connections available to process queries. When all connections are in use, subsequent queries will be queued, which can result in longer load times.

You can identify connection pool bottlenecks by comparing query execution time to total runtime in your dashboard metrics. If there's a significant difference between these times, it likely indicates your queries are waiting for available connections.

Performance Optimization Tips

  1. Query Optimization: Review and optimize your SQL queries to ensure they're running efficiently. Complex queries or those pulling large amounts of data can impact performance.

  2. Dashboard Organization: Consider breaking up dashboards with many charts into smaller, more focused views to reduce concurrent query load.

  3. Connection Pool Adjustment: If you continue experiencing slowdowns, contact support to evaluate whether increasing the connection pool size would benefit your use case.

If you'd like to increase or decrease the number of connections that we make to your database, please reach out to support and we'll be glad to adjust.

Note: While increasing connection pool size can improve concurrent query performance, it should be balanced against database resource constraints. Work with our support team to find the optimal configuration for your needs.