| From: | Sam Gendler <sgendler(at)ideasculptor(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Nicolas Charles <nicolas(dot)charles(at)normation(dot)com>, pgsql-performance(at)lists(dot)postgresql(dot)org, Peter Geoghegan <pg(at)bowt(dot)ie>, Shijia Wei <shijiawei(at)utexas(dot)edu>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Subject: | Re: Consecutive Query Executions with Increasing Execution Time |
| Date: | 2019-12-17 00:53:31 |
| Message-ID: | CAEV0TzAb3uwSXSy-s2b_0AP+9DtMSKbD0xci0eVoyEwHvZ0OTA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Mon, Dec 16, 2019 at 2:48 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> unless you suppose it actually
> throttled to below base freq, which surely shouldn't happen that fast.
> Might be worth watching the CPU frequency while doing the test though.
>
Wouldn't expect to see such linear progression if that were the case.
Steps, over a relatively long period of time, would be the likely pattern,
no? Same goes for some other process fighting for resources. Every
iteration requiring what appears to be a fairly constant increase in
execution time (2-5ms on every iteration) seems an unlikely pattern unless
the two processes are linked in some way, I would think.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kaijiang Chen | 2019-12-17 02:58:17 | weird long time query |
| Previous Message | Tom Lane | 2019-12-16 22:48:16 | Re: Consecutive Query Executions with Increasing Execution Time |