| From: | "Ing(dot) Marcos Ortiz Valmaseda" <mlortiz(at)uci(dot)cu> |
|---|---|
| To: | Anne Rosset <arosset(at)collab(dot)net> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Queries becoming slow under heavy load |
| Date: | 2011-01-25 22:27:01 |
| Message-ID: | 51831170.52414881295994420979.JavaMail.root@ucimail4.uci.cu |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
When you say that with a lot of concurrent access, queries get very slow, How many concurrent connections to your server have you had?
more that max_connections´value?
If you want to have many concurrent connections, you should have consider to use a pooling connection system like pgbouncer or pgpool.
Which are the values for:
- work_mem
- shared_buffers
- maintenance_work_mem
- effective_cache_size
- effective_io_concurrency
- server_version
Which are your platform?
Regards
--
Ing. Marcos Luís Ortíz Valmaseda
System Engineer -- Database Administrator
Centro de Tecnologías de Gestión de Datos (DATEC)
Universidad de las Ciencias Informáticas
http://postgresql.uci.cu
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2011-01-26 01:32:45 | Re: Running PostgreSQL as fast as possible no matter the consequences |
| Previous Message | Andy Colson | 2011-01-25 22:12:45 | Re: Queries becoming slow under heavy load |