Good afternoon! I was reading a little bit about h...
# questionsp
pablo.pazos
06/16/2025, 7:05 PMGood afternoon! I was reading a little bit about how to monitor database connections and stumbled upon HikariCP, that seems to be an alternative to Tomcat JDBC Pool, which seems to be the default in Grails. Does using HikariCP provide any advantage above the default for Grails?
What I read is basically: HikariCP consumes less memory, it can be monitored easier, and has more options for configuration. Does someone here actually use it? Noticed any difference?
j
James Fredley
06/16/2025, 7:11 PMIt makes a HUGE difference.
HikariCP is the default in Grails 7 generated applications.
p
pablo.pazos
06/16/2025, 7:13 PMWhen you have time, can you point out in which areas it makes a difference?
pablo.pazos
06/16/2025, 7:14 PMI'm still in Grails 5.x and if this is something that improves my user's experience, I would gladly change it.
j
James Fredley
06/16/2025, 7:16 PMhttps://github.com/brettwooldridge/HikariCP has a lot of great info
p
pablo.pazos
06/16/2025, 7:17 PM🙌
j
James Fredley
06/16/2025, 7:17 PMp
pablo.pazos
06/16/2025, 7:22 PMcool thanks
pablo.pazos
06/16/2025, 7:24 PMthey mention the tcp keepalive must be set, in the PR I don't see a reference to that, isn't that needed?
pablo.pazos
06/16/2025, 7:24 PM(even for the default H2 connections)
j
James Fredley
06/16/2025, 7:51 PMThat is a driver level setting (tcpKeepAlive=true), which we could add to generated application in grails-forge. Can you create an issue and/or PR to add it there for each support DB?
https://github.com/apache/grails-forge/tree/7.0.x/grails-forge-core/src/main/java/org/grails/forge/feature/database
p
pablo.pazos
06/16/2025, 8:25 PMsure
pablo.pazos
06/16/2025, 8:31 PM