- Newest
- Most votes
- Most comments
Hello.
Based on your test results, it is highly likely that the AWS-LC-FIPS 2025 CPU Jitter Entropy initialization is involved.
There is an existing performance-related issue in AWS-LC similar to this phenomenon.
Although it has already been closed, it is possible that performance degradation could still occur.
https://github.com/aws/aws-lc-rs/issues/899
The aws-lc-rs README notes a "one-time-per-process" latency cost associated with CPU Jitter Entropy—typically around 50 ms—so it is certainly possible that aws-lc-rs is the cause of the slowdown.
https://github.com/aws/aws-lc-rs/blob/main/book/src/resources.md
When set to 1, disables the CPU jitter entropy source in the build. This affects the random number generation subsystem. Use of jitter entropy has a one-time-per-process latency cost, typically around 50ms, for the collection of entropy. This flag may be used to eliminate this latency.
The ~27 ms per-backend process startup cost you're observing on RDS PostgreSQL 17.11 and 18.6 (versus ~4.5 ms on 14.19) is indeed significant for connection-heavy workloads. Each PostgreSQL backend is a full process that requires forking, copying memory structures, initializing process state, and authentication. When your API opens 40–120 new connections per second, this fixed startup cost is paid continuously and can lead to substantial CPU consumption.
Your observation that the regression appeared specifically in the August 2026 minor releases (17.11 and 18.6) while 18.4 remained clean is valuable diagnostic information. The timing and cross-version nature of the issue does suggest an infrastructure-layer change rather than a PostgreSQL core regression.
Regarding process forking overhead, parallel query execution provides a useful analogy for understanding the costs involved. Each parallel worker is a full PostgreSQL backend process requiring process forking and authentication, consuming connection slots from your max_connections limit. Each worker also consumes its own memory, including work_mem for operations. Under high concurrency, this can lead to CPU saturation, increased context switching, and connection exhaustion.
For your specific situation with connection-heavy workloads, your mitigation strategy of raising the connection-pool idle timeout to reduce the new-connection rate from ~124/s to ~57/s is sound. Additional strategies to consider include implementing connection pooling if not already in place, as frequent opening and closing of database connections without pooling can cause elevated authentication attempts and slow connection establishment times. You might also evaluate whether your application can maintain longer-lived connections or use a connection pooler like PgBouncer or RDS Proxy to reduce the frequency of new backend process creation.
For your specific questions about the AWS-LC-FIPS change and whether this represents a new baseline, I recommend opening a support case through the AWS Support Center at https://console.aws.amazon.com/support/ where the RDS team can investigate the specific build changes in those minor releases and provide guidance on any available mitigations or upcoming fixes. When you add correspondence to your support case, include the detailed version comparison data and timing information you've gathered, as this will help the team investigate efficiently.
Sources
Initial troubleshooting for common PostgreSQL performance issues in Aurora PostgreSQL - Amazon Aurora
Best Practices for Parallel Queries in RDS for PostgreSQL - Amazon Relational Database Service
answered 2 months ago
Relevant content
asked 9 months ago
asked 3 years ago

Hello. Thanks for sharing. I'm pretty sure that tha's the cause I hope AWS will fix it for RDS