From ed727a2740b50d5ca49fdfad805f7e2c4498cec5 Mon Sep 17 00:00:00 2001 From: Michael Raney Date: Mon, 8 Jun 2026 14:19:39 -0400 Subject: [PATCH] Fix connection pool math in Spring example config comments The previous comment stated "3 * 3 endpoints = 9 connections = 27,000 rps" but the config connects to the public endpoint which exposes 9 peers, not 3. Updated to reflect correct public endpoint math and added note about VPC endpoint differences. Also aligned with the documented best practice of targeting 500 requests/sec per connection rather than the 3,000 hard limit. --- .../spring/src/main/resources/keyspaces-application.conf | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/java/datastax-v4/spring/src/main/resources/keyspaces-application.conf b/java/datastax-v4/spring/src/main/resources/keyspaces-application.conf index 773ece9..af428c9 100644 --- a/java/datastax-v4/spring/src/main/resources/keyspaces-application.conf +++ b/java/datastax-v4/spring/src/main/resources/keyspaces-application.conf @@ -43,9 +43,10 @@ datastax-java-driver { hostname-validation = false } - # For every connection, Amazon Keyspaces allows 3000 request per connection per endpoint - # If pool.local.size = 3 * 3 endpoints = 9 total connections for session - # For 9 connections at 3000 request per connection for a total of 27,000 rps + # Amazon Keyspaces supports up to 3000 CQL requests per connection per second. + # Public endpoints expose 9 peers: pool.local.size = 3 * 9 endpoints = 27 connections. + # VPC endpoints typically expose 2-5 peers (most commonly 3). + # At 500 requests/sec per connection (recommended), 27 connections support 13,500 rps. advanced.connection.pool.local.size = 3 } \ No newline at end of file