| From: | Karl Czajkowski <karlcz(at)isi(dot)edu> |
|---|---|
| To: | Rick Otten <rottenwindfish(at)gmail(dot)com> |
| Cc: | "Kevin(dot)Hughes(at)uk(dot)fujitsu(dot)com" <Kevin(dot)Hughes(at)uk(dot)fujitsu(dot)com>, "pgsql-performa(dot)" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Client Server performance & UDS |
| Date: | 2017-05-30 20:20:46 |
| Message-ID: | 20170530202046.GE7575@moraine.isi.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On May 30, Rick Otten modulated:
> If your clients are keeping persistent connections open to the
> database, and the latency you are experiencing is within the
> transaction itself, you might look at disk I/O for your WAL (write
> ahead logs) and take a closer look at WAL and checkpoint tuning.
>
Also, if you are doing similar operations over and over with literal
data in them, you may have more query planner overhead per transaction
than if you prepared statements when opening the persistent connection
and then simply executed the statements over and over with different
parameters for each request.
Karl
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nikolay Samokhvalov | 2017-06-03 08:37:05 | Re: Monitoring tool for Postgres Database |
| Previous Message | Justin Pryzby | 2017-05-30 10:52:15 | Re: join estimate of subqueries with range conditions and constraint exclusion |