For how long does Prisma keep idle connections aro...
# orm-helpj
Julien Goux
03/16/2022, 4:04 PMFor how long does Prisma keep idle connections around in the context of postgresql?
Julien Goux
03/16/2022, 4:09 PMI found an undocumented parameter max_idle_connection_lifetime defaulting to 5m https://github.com/prisma/docs/issues/1657
Julien Goux
03/16/2022, 4:09 PMIs it used today by prisma?
Julien Goux
03/16/2022, 4:09 PMBecause it’s been 5 min and we are still seeing our 3 idle connections
d
dpetrick
03/16/2022, 4:15 PMThis setting may be a little confusing, the connections will not be immediately removed from the pool but they are lazily dropped and recreated if that connection is touched again if it exceeded that lifetime.
j
Julien Goux
03/16/2022, 4:38 PMso if there is no activity on my server, the connections won’t be closed even after 5 min?
Julien Goux
03/16/2022, 4:38 PMit’s the next time Prisma is doing something that it will cleanup the connections?
Julien Goux
03/16/2022, 4:38 PMI thought there was a kind of setTimeout() somewhere that fired after 5min
d
dpetrick
03/16/2022, 4:43 PMprisma never actively closes connections (which has its own benefits and drawbacks) but in general, the closing of idle connections is a matter of db configuration for us right now.
dpetrick
03/16/2022, 4:43 PMthe idle time just tells the prisma connection pool to reconnect after that idle time
dpetrick
03/16/2022, 4:44 PMthis is needed for, say, google sql because they force close connection after a given time. to prevent failing queries we allow you to configure the pool so that we work around that
j
Julien Goux
03/17/2022, 8:23 AMwhat’s the point of dropping + recreating the connection in one go? Shouldn’t connections be freed if not used after some time?
If we set a max_connections at something like 10, will prisma eagerly open 10 connections and maintain those 10 connections all the time?
d
dpetrick
03/17/2022, 11:42 AMwhat’s the point of dropping + recreating the connection in one go? Shouldn’t connections be freed if not used after some time?This directly relates to my previous message, it's about circumventing platform issues where databases kill connections after a given time, which would lead to intermittent issues if the pool hits a connection like that. The current pool does no asynchronous housekeeping, which is why everything is lazily evaluated when a connection is touched.
If we set a max_connections at something like 10, will prisma eagerly open 10 connections and maintain those 10 connections all the time?The pool is not eagerly filled, only with more requests coming in will the pool increase in size until max is hit.
Shouldn’t connections be freed if not used after some time?We have internal back and forth discussions about this. I can't disclose more right now, but we're actively discussion the pooling situation.
14 Views