From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Nicolas Charles <nicolas(dot)charles(at)normation(dot)com> |
Cc: | 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-16 22:48:16 |
Message-ID: | 28107.1576536496@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Nicolas Charles <nicolas(dot)charles(at)normation(dot)com> writes:
> Could it be that your CPUs is warming and throttling? You didn't mention the platform used, so I'm not sure whether it's a server or a laptop
Hmm, that's an interesting thought. The OP did say the CPU type,
but according to Intel's spec page for it [1] the difference between
base and turbo frequency is only 4.0 vs 4.2 GHz, which doesn't seem
like enough to explain the results ... 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.
I was speculating about some OS-level problem myself. Plain old "top"
might be enough to show relevant info if it's in that area.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Sam Gendler | 2019-12-17 00:53:31 | Re: Consecutive Query Executions with Increasing Execution Time |
Previous Message | Nicolas Charles | 2019-12-16 22:08:52 | Re: Consecutive Query Executions with Increasing Execution Time |