Connection Pooling in AEM

Consider checking logs and thread dumps for any long waiting threads - connection pooling.

Are you using any tool to monitor your connection pool usage.

This can help you see how many connections are being used at peak times and whether your application is frequently waiting for a connection to become available.

Given your scenario with approximately 24,000 users logging into the site during events, along with multiple publishers and dispatchers, you may need to increase the number of connections in your connection pooling configuration to ensure adequate capacity during peak loads. However, it's essential to balance this with the capabilities of your database server(s) and the overall performance of your AEM application.
let's assume:

• Expected concurrency level: 100 simultaneous database connections
• Maximum connections per pool: 50

Number of connection pools required = Expected concurrency level / Maximum connections per pool Number of connection pools required = 100 / 50 = 2

So, in this example, you would need at least 2 connection pools to support 100 simultaneous database connections.

Keep in mind that this is a simplified calculation, and in a real-world scenario, you might need to adjust based on factors such as peak loads, database performance, and application architecture.
Start by reviewing your database server's capacity and performance metrics under load, then gradually increase the number of connections in your connection pooling configuration while monitoring system performance and resource utilization. Perform load testing to validate the effectiveness of your configuration adjustments and ensure that your AEM application can handle peak loads efficiently without impacting performance or causing resource contention issues.