Running the limitless performance test with the AWS wrapper results in a CPU spike

[jkwuc89]

Describe the bug

I configured JMeter inside my Windows Server 2022 EC2 instance to run the performance tests using the driver without any plugins and the driver with the limitless plugin.

My Aurora limitless instance is configured as follows:

* Engine: 16.4-limitless
* Minimum capacity: 64 ACUs (128 GiB)
* Maximum capacity: 1501 ACUs (3002 GiB)
* Transaction routers: 4
* Shards: 4
    * Additional routers and shards beyond the default of 2 for each were created using the following.
        https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/limitless-add-router.html
        https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/limitless-shard-split.html
* Region: us-east-2

The screencast below shows the tests running with the base driver. Observe that JMeter is able to update itself with the test progress and the CPU usage does not spike.

limitless_no_plugin.mov

The screencast below shows the tests running with the AWS wrapper and the limitless plugin. Observe that JMeter no longer updates itself, and Task Manager no longer updates itself. When the test completes, Task Manager shows that the CPU usage spiked to 100% during the test run.

limitless_plugin.mov

The screencast below shows the tests running with the AWS wrapper with no plugins. Observe that the CPU still spikes but not as severe as when the limitless plugin is used.

limitless_aws_driver_no_plugins.mov

Expected Behavior

Using the AWS wrapper should not cause the CPU utilization to spike. CPU utilization should be more or less comparable to using base driver without the AWS wrapper.

What plugins are used? What other connection properties were set?

limitless

Current Behavior

Please refer to the bug description above.

Reproduction Steps

1. Configure JMeter to run the performance tests.
2. The start of each screencast above shows how the JDBC connections should be configured. Attached below is the JMeter test plan that can be used as a starting point.
3. Run the JMeter test.

Limitless Performance.jmx.zip

Possible Solution

No response

Additional Information/Context

No response

The AWS Advanced JDBC Driver version used

2.5.3

JDK version used

OpenJDK 64-Bit Server VM Corretto-17.0.13.11.1 (build 17.0.13+11-LTS, mixed mode, sharing)

Operating System and version

Windows 2022 Server EC2 m7a.xlarge (4 vCPUs, 16 GB of memory)