If you want to test it with same connection parameters, make one big pool num_init_children = 96 max_pool = 1 (supposing that you have max_connection on 100 (while 4 reserved for superuser))
With this configuration you can start pgbench with -c 96 :) max_pool * num_init_children <= max_connection - superuser_reserved_connection maximum connections + max_pool*num_init_children <= (max_connections - superuser_reserved_connections) (no query canceling needed) On Wed, Oct 12, 2011 at 8:27 PM, Matias Israel Malpica Escobar < [email protected]> wrote: > Hum i see, so it is supposed to do that right, ok so if i want to do a > sizing for the maximux of conections i can have for my server how could i do > it? How could i test pooling then? > > ------------------------------ > *De:* Armin Nesiren [[email protected]] > *Enviado el:* miércoles, 12 de octubre de 2011 01:22 p.m. > > *Para:* Matias Israel Malpica Escobar > *CC:* [email protected] > *Asunto:* Re: [Pgpool-general] PGpool not pooling... > > yes, but.. pgbench stops (not quits) when reach maximum number of > connections.. that means > pgpool is waiting to quit first connection before allowing another client > to connect. > > But, there are 3 x 33 more child processes that are waiting for > connection but > with different connection parameters ( *postgres: testuser Matt > 127.0.0.1(55016) idle in transaction - *this should be reserved for > that...) > > > On Wed, Oct 12, 2011 at 8:13 PM, Matias Israel Malpica Escobar < > [email protected]> wrote: > >> *# number of pre-forked child process >> num_init_children = 33* >> *# Number of connection pools allowed for a child process >> max_pool = 4 >> * >> i know that number is set to 33 while im trying to connect 34 but it >> should put in a queue right? >> * >> ------------------------------ >> **De:* Armin Nesiren [[email protected]] >> *Enviado el:* miércoles, 12 de octubre de 2011 01:14 p.m. >> *Para:* Matias Israel Malpica Escobar >> *CC:* [email protected] >> *Asunto:* Re: [Pgpool-general] PGpool not pooling... >> >> What is your values for >> num_init_childern and max_pool >> in pgpool.conf ? >> >> On Wed, Oct 12, 2011 at 8:00 PM, Matias Israel Malpica Escobar < >> [email protected]> wrote: >> >>> HI i am testing pgpool with pgbench, i am running the following: >>> >>> *pgbench Matt -U testuser -p 9999 -c 34 -t 10 -C -d >>> * >>> An i am noticing that when the conection goes up to the 32 client it >>> stops working >>> >>> *client 32 executing \setrandom delta -5000 5000 >>> client 32 sending BEGIN;* >>> when i go to ps -aux i can see this in each process >>> >>> *postgres: testuser Matt 127.0.0.1(55016) idle in transaction* >>> >>> i already checked the pgpool.conf file and the maximun child conections >>> option is set to 32 but from what i understand pgpool should put the >>> remaining 2 conecntions in queue right? >>> >>> *connection_cache = true* >>> What am i doing worng??? >>> >>> _______________________________________________ >>> Pgpool-general mailing list >>> [email protected] >>> http://pgfoundry.org/mailman/listinfo/pgpool-general >>> >>> >> >> >> -- >> Armin >> > > > > -- > Armin > -- Armin
_______________________________________________ Pgpool-general mailing list [email protected] http://pgfoundry.org/mailman/listinfo/pgpool-general
