how expensive is constantly opening and closing a connection to mysql?

Question

I have a python script that is currently connecting to my mysql database every 60 seconds, checking something, then closing the connection, so every minute I am doing this open/close of the connection. Is it more expensive for me to do this, or to just leave the connection open since I'm executing my code so frequently?

What are the upsides and downsides of keeping the connection open for maybe 8 hours at a time, or opening and closing it 480 times over the course of those eight hours?

Ideally you keep a connection pool, it saves a lot of overhead. Once a minute won't kill you, but once every request might if you're getting hundreds of requests per second. — tadman
– tadman, Commented Feb 1, 2017 at 19:01

Archimedes Trajano · Accepted Answer · 2025-11-28 05:09:59Z

0

Even if it is more expensive, it is better doing it the way you have it because you're holding a connection for a shorter period to allow other connections to come in.

It will be more resilient to database restarts as well.

answered yesterday

Archimedes Trajano

43.2k29 gold badges222 silver badges372 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

how expensive is constantly opening and closing a connection to mysql?

1 Answer 1

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related