Skip to content

Fix connection pool math in Spring example config comments#62

Open
michaelraney wants to merge 1 commit into
aws-samples:mainfrom
michaelraney:fix/connection-pool-math-comment
Open

Fix connection pool math in Spring example config comments#62
michaelraney wants to merge 1 commit into
aws-samples:mainfrom
michaelraney:fix/connection-pool-math-comment

Conversation

@michaelraney

Copy link
Copy Markdown
Contributor

Summary

  • Corrected the connection pool math comment in the Spring example's keyspaces-application.conf
  • Previous comment assumed 3 endpoints (VPC scenario) but the config connects to the public endpoint which exposes 9 peers
  • Updated to reflect correct public/VPC endpoint counts and aligned with the documented best practice of 500 requests/sec per connection

What Changed

The comment block above advanced.connection.pool.local.size = 3 previously stated:

# 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

Updated to:

# 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.

References

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant