Hi,
On 2019-12-16 17:48:16 -0500, Tom Lane wrote:
> 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 ..
On Mon, Dec 16, 2019 at 2:48 PM Tom Lane 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 cas
Nicolas Charles 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
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
Nicolas
Le 16 décembre 2019 21:50:17 GMT+01:00, Tom Lane a écrit :
>Peter Geoghegan writes:
>> Why do the first and the twentieth executions of the q
Peter Geoghegan writes:
> Why do the first and the twentieth executions of the query have almost
> identical "buffers shared/read" numbers? That seems odd.
It's repeat execution of the same query, so that doesn't seem odd to me.
This last set of numbers suggests that there's some issue with the
On Mon, Dec 16, 2019 at 9:28 AM Shijia Wei wrote:
> 1st Query:
> Buffers: shared hit=17074 read=16388
> 20th Query:
> Buffers: shared hit=17037 read=16390
Why do the first and the twentieth executions of the query have almost
identical "buffers shared/
po 16. 12. 2019 v 14:02 odesílatel Mariel Cherkassky <
mariel.cherkas...@gmail.com> napsal:
> I see, thank u !
> Maybe I didnt see big difference because most of my tables arent so big.
> My db`s size is 17GB and the largest table contains about 20M+ records.
>
Postgres 12 has enabled JIT by defa
Hi Laurenz,
Each time the identical query executes, the total number of rows selected
stays the same. The table is actually not modified between/during runs.
The query plan stays the same between fast and slow runs. Please find two
copied here:
The first one is the output of the first query in th
Shijia Wei writes:
> I am running TPC-H on recent postgresql (12.0 and 12.1).
> On some of the queries (that may involve parallel scans) I see this
> interesting behavior:
> When these queries are executed back-to-back (sent from psql interactive
> terminal), the total execution time of them incre
On Sun, 2019-12-15 at 23:59 -0600, Shijia Wei wrote:
> I am running TPC-H on recent postgresql (12.0 and 12.1).
> On some of the queries (that may involve parallel scans) I see this
> interesting behavior:
> When these queries are executed back-to-back (sent from psql interactive
> terminal), the
I see, thank u !
Maybe I didnt see big difference because most of my tables arent so big. My
db`s size is 17GB and the largest table contains about 20M+ records.
Thanks again !
Hi there –
I have no idea why this happening. But I suspect the parallel requires more
internal machine resources like CPU etc because you can faster retrieve the
disk data from the one hand but you ought to spend more resources for
maintaining several threads and theirs coordination (px coordi
Hey Jeff,Andrew,
I continued testing the 12version vs the 96 version and it seems that there
is almost non diff and in some cases pg96 is faster than 12. I compared the
content of pg_stat_statements after each test that I have done and it seems
that the db time is almost the same and sometimes 96 i
Hi Shijia,
If you're using fish, I suspect you're on a Mac - I don't have experience
on this platform.
Can you check with pgAdmin (3 or 4) what the server is busy doing after a
few iterations? Check for locks, as it could be a cause. Also, do you have
concurrent INSERTs?
Olivier
On Mon, Dec 16,
Hi Olivier,
I do not think that the queries are executed concurrently. The bash for
loop ensures that the next command fires only after the first returns.
Also for some 'complex' queries, even a wait-period that is longer than the
total execution time does not completely avoid this effect.
For exa
Hi Shijia,
It sounds like concurrency on the queries: the second starts before the
first ends, and so on. With a short wait in between you ensure sequential
execution. Notice that you also have the overhead of concurrent psql...
Sounds normal to me.
Best regards
Olivier
On Mon, Dec 16, 2019, 0
16 matches
Mail list logo
