DBeaver UI Thread vs. JDBC Connection Pool: How Does Concurrent Query Execution Affect Latency?

When multiple SQL statements are submitted simultaneously in DBeaver, the single UI thread becomes a bottleneck while the underlying JDBC connection pool may reach its maximum size, causing increased latency. The modal 'Execute SQL' dialog serializes executions, and large result sets can be fully buffered, further amplifying delay. How does UI thread contention interact with connection pool saturation under concurrent client requests? What configuration adjustments could reduce this latency without changing driver defaults? Is there a reliable method to measure UI thread impact versus driver pool limits in DBeaver?