You're opening a connection for each iteration?

1,095 registered users | 0 active users | 0 LpH | Statistics
Login | Create New User

Welcome to IWETHEY!

Post #189,395 by admin 1/8/05 10:20:34 AM Reply	You're opening a connection for each iteration? Pooling is where it's at, ma man... :-) Regards, -scott anderson "Welcome to Rivendell, Mr. Anderson..."
Post #189,418 by FuManChu 1/8/05 2:29:14 PM Reply	:) It does pooling But it does so optimistically: 1. If there's an (already open) connection in the pool, it gets popped and used. 2. If there isn't a conn ready right away, a new conn is made. 3. When the thread is finished with the conn, it tries to push it into the pool. 4. If the pool is full (mine was max 10), the free conn is closed and discarded. The 37 connections are far less than the total number of statements. ;) This is testing code, ma man.
Post #189,424 by admin 1/8/05 3:38:43 PM Reply	Okey Doke That wasn't entirely clear from the post. When I use Postgres, I keep my maximum connections very high, on the theory that if I hit a peak once, I'm likely to do it again. Or use a sufficiently slow decay time. Regards, -scott anderson "Welcome to Rivendell, Mr. Anderson..."

Simple ORM data points - (FuManChu) - (4) - Jan. 5, 2005, 05:50:32 PM EST

Well, that explains Postgres - (FuManChu) - (3) - Jan. 8, 2005, 12:46:03 AM EST

You're opening a connection for each iteration? - (admin) - (2) - Jan. 8, 2005, 10:20:34 AM EST

:) It *does* pooling - (FuManChu) - (1) - Jan. 8, 2005, 02:29:14 PM EST

Okey Doke - (admin) - Jan. 8, 2005, 03:38:43 PM EST

Yousa steala precious from meesa!
62 ms