But I got error in jdbc/db-do-commands. It reports error:

The log 这个 ResultSet 已经被关闭。 means This ResultSet is already closed.

What happened? This code If I changed to MySQL, it works fine.

@stardiviner could you try

(jdbc/db-do-commands postgresql-db false
                        [fruit-table-ddl
                         "CREATE INDEX name_idx ON fruit ( name );"])

what would you guys say between hikari and c3p0?

@seancorfield thanks for the previous tip, that worked really well, im just trying to improve the pool now

We use c3p0 happily in a high traffic production environment. We have not tried Hikari so I can't compare them. We did try BoneCP tho' -- that seemed faster overall than c3p0 but we saw fairly massive memory spikes during high traffic use so we went back to c3p0.

I would say try both c3p0 and Hikari and see which works better for you -- swapping connection pool libraries is pretty easy (assuming you have a function that turns DB access information into a {:datasource connection-pool} style db-spec 🙂

yeah… I`m using like that

Im trying out hikari now

Hikaricp is advertised (and was benchmarked by a few) as the fastest and more efficient of the 2

But sadly there some “heavy” query that makes jump from 80ms to 300ms to get the data

Happy hikaricp user here (prod/high volume as well)

Thanks @mpenet for the insight, im gonna check it for sure

But yeah c3p0 is likely quite good as well, doubt you can go wrong with these 2

I’m doing some tests right now on it, on my dev it was awesome, on production i still cant tell

So… question about connection pool, if I put 100 at max, means that it can create 100 connections??? 100 threads?

100 max what? You can control all sorts of aspects of a connection pool. Consult the documentation for details.