Giter Site home page Giter Site logo

Comments (4)

juhlig avatar juhlig commented on July 19, 2024 1

Sounds good to me :) Setting the connect strategy to lazy allows workers to (re-) start more quickly and reliably, and works around poolboy's annoying deficiency to crash an entire pool if one worker fails to (re-) start, too.

One ugliness that remains is that part of it (the idle timeout) depends on the server, ie there is no way for the client to decide that it wants to be extra nice and close the connection when it has not been used for a while (maybe even to just close and revert to the not-connected state of lazy mode).

from mysql-otp-poolboy.

zuiderkwast avatar zuiderkwast commented on July 19, 2024

@getong, @juhlig, other users, what's your opinion on this?

from mysql-otp-poolboy.

zuiderkwast avatar zuiderkwast commented on July 19, 2024

and works around poolboy's annoying deficiency to crash an entire pool if one worker fails to (re-) start, too

Yes, I didn't even think about this. It's an extra benefit.

maybe even to just close and revert to the not-connected state of lazy mode

Hm... Then we lose the connection state, but as a non-default option with an explicit warning, perhaps yes. Anyway, with just the server disconnecting after 8 hours idle, the application will come to some balance of how many connections it needs within 24 hours.

from mysql-otp-poolboy.

juhlig avatar juhlig commented on July 19, 2024

and works around poolboy's annoying deficiency to crash an entire pool if one worker fails to (re-) start, too

Yes, I didn't even think about this. It's an extra benefit.

Oh, plus it has the benefit that workers will always start quickly. With poolboy, worker starts happen synchronously, blocking all other pool operations, so quick worker starts are good :)

maybe even to just close and revert to the not-connected state of lazy mode

Hm... Then we lose the connection state, but as a non-default option with an explicit warning, perhaps yes.

Just a thought, I think not really worth it.

Anyway, with just the server disconnecting after 8 hours idle, the application will come to some balance of how many connections it needs within 24 hours.

I guess so :) In any case, I think that this would be a good improvement, so I'm in favor of it :)

from mysql-otp-poolboy.

Related Issues (15)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.