Re: Postgresql 14 performance - Mailing list pgsql-admin

From Kenny Bachman
Subject Re: Postgresql 14 performance
Date
Msg-id CAC0w7L+GFza2xyAt-4SQwsMbQWAUqCf7tp+k5gOQZ6hwknDh3w@mail.gmail.com
Whole thread Raw
In response to Re: Postgresql 14 performance  (Mladen Gogala <gogala.mladen@gmail.com>)
Responses Re: Postgresql 14 performance  (Mladen Gogala <gogala.mladen@gmail.com>)
List pgsql-admin
The huge_pages parameter is try. How can I know the huge page is used for shared buffers?
Also, I would like to say one more thing. Some queries have high planning time of explain analyze output. However, I run vacuumdb analyze command every day. I am a little bit confused about this.

Warm regards,
Kenn

Mladen Gogala <gogala.mladen@gmail.com>, 22 Ağu 2022 Pzt, 15:56 tarihinde şunu yazdı:
On 8/21/22 21:16, Mladen Gogala wrote:

Agreed. The "perf top" output produced by Kenny definitely indicates that. That's precisely why I concentrated on JIT. Anything else would give us a slim chance of increasing the query speed.

When I come to think of it, are you using huge pages for shared buffers? Huge pages tend to decrease page tables and lessen the impact of paging.

Regards

-- 
Mladen Gogala
Database Consultant
Tel: (347) 321-1217
https://dbwhisperer.wordpress.com

pgsql-admin by date:

Previous
From: Mladen Gogala
Date:
Subject: Re: Postgresql 14 performance
Next
From: Sbob
Date:
Subject: DB Encoding question