public inbox for [email protected]  

help / color / mirror / Atom feed

autovacuum_vacuum_cost_delay
2+ messages / 2 participants
[nested] [flat]

* autovacuum_vacuum_cost_delay
@ 2024-07-09 11:38 Shenavai, Manuel <[email protected]>
  2024-07-09 13:42 ` Re: autovacuum_vacuum_cost_delay Muhammad Ikram <[email protected]>
  0 siblings, 1 reply; 2+ messages in thread

From: Shenavai, Manuel @ 2024-07-09 11:38 UTC (permalink / raw)
  To: pgsql-general

Hi everyone,

We are doing some tests with different autovacuum settings.

Looking at autovacuum_vacuum_cost_delay:
https://www.postgresql.org/docs/current/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-COST-DE...

Can someone help to understand what a high or low value of this setting really means? Would it be OK to set this to 0? If not, why not?

Thanks in advance &
Best regards,
Manuel


^ permalink  raw  reply  [nested|flat] 2+ messages in thread

* Re: autovacuum_vacuum_cost_delay
  2024-07-09 11:38 autovacuum_vacuum_cost_delay Shenavai, Manuel <[email protected]>
@ 2024-07-09 13:42 ` Muhammad Ikram <[email protected]>
  0 siblings, 0 replies; 2+ messages in thread

From: Muhammad Ikram @ 2024-07-09 13:42 UTC (permalink / raw)
  To: Shenavai, Manuel <[email protected]>; +Cc: pgsql-general

Hi Shenvail,

Based on what I could understand,

Lower value will cause more frequent run of Autovacuum. Will have
less delay between processing data chunks but will put more load on the I/O
system. Autovacuum tasks will complete faster. Cleanup of dead tuples and
blots will be quicker thus increasing performance in the cases where tables
are heavily updated/deleted.

Higher values will result in longer delays between processing data chunks
thus slowing down the completion of autovacuum tasks. Autovacuum will have
less I/O load for its tasks. Database performance will be degraded if
operations are more update/delete intensive. Dead tuples and bloat will
take longer to be cleaned up.
It can be beneficial  for performance of other database operations,
especially if your system is I/O-bound. Can also be helpful when system
resources are less

Regards,
Muhammad Ikram
Bitnine Global.


On Tue, Jul 9, 2024 at 4:38 PM Shenavai, Manuel <[email protected]>
wrote:

> Hi everyone,
>
>
>
> We are doing some tests with different autovacuum settings.
>
>
>
> Looking at autovacuum_vacuum_cost_delay:
>
>
> https://www.postgresql.org/docs/current/runtime-config-autovacuum.html#GUC-AUTOVACUUM-VACUUM-COST-DE...
>
>
>
> Can someone help to understand what a high or low value of this setting
> really means? Would it be OK to set this to 0? If not, why not?
>
>
>
> Thanks in advance &
> Best regards,
>
> Manuel
>


-- 
Muhammad Ikram


^ permalink  raw  reply  [nested|flat] 2+ messages in thread

end of thread, other threads:[~2024-07-09 13:42 UTC | newest]

Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2024-07-09 11:38 autovacuum_vacuum_cost_delay Shenavai, Manuel <[email protected]>
2024-07-09 13:42 ` Muhammad Ikram <[email protected]>

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox