"We create a connection pool, then take a connection from the pool for every session, we never release it and if we run out of connections we create more. Max connections is set to unlimited. WCGW?"
And then: "your database can't handle the load"

-
-
-
I've had a convo that went Me: If you are spinning up app instances on demand you definitely should be using connection pooling Later: There appears to be a new pool for each new app instance :(
- Još 2 druga odgovora
Novi razgovor -
-
-
The goal should always be maximum stable throughout. That would size the connection based on resources available not user counts. High connection counts can work at low load, but they will always end badly.
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
Amen! My mantra for scalability testing: set connection pool to 1, rewrite everything
to get the most out of that connection, then increase the pool slowly until you get diminishing returns.Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
I’d say: the goal of a connection pool is to limit the nr of new connections created
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.
principal consultant & database evangelist at 


