You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think the Readme is quite unclear about what database these connection pools are actually testing against. When I try to run the command ./benchmark.sh quick -p pool=hikari -p jdbcUrl=jdbc:postgresql://rdsHost/database I don't actually see the number of connection to my RDS increase. How is it actually testing these pools? Are there different params I should be passing in to actually test these pools against my hardware?
Sorry if I'm being dumb, I'm simply trying to test how a bunch of database pools would perform against our hardware. I'd also like to test Hikari against tools like pgbouncer and AWS Proxy which are standalone connection poolers. Thank you for the help!
The text was updated successfully, but these errors were encountered:
Hello,
I think the Readme is quite unclear about what database these connection pools are actually testing against. When I try to run the command
./benchmark.sh quick -p pool=hikari -p jdbcUrl=jdbc:postgresql://rdsHost/database
I don't actually see the number of connection to my RDS increase. How is it actually testing these pools? Are there different params I should be passing in to actually test these pools against my hardware?Sorry if I'm being dumb, I'm simply trying to test how a bunch of database pools would perform against our hardware. I'd also like to test Hikari against tools like pgbouncer and AWS Proxy which are standalone connection poolers. Thank you for the help!
The text was updated successfully, but these errors were encountered: