search

cloud-bulldozer / benchmark-operator

The Chuck Norris of cloud benchmarks
Apache License 2.0
282 stars 127 forks source link

disable hammerdb postgreSQL autovacuum #801

Closed ebattat closed 1 year ago

ebattat commented 1 year ago

Description

Disable autovacuum for improving PostgreSQL performance

Fixes

  1. Adding autovacuum = off: The hammerdb framework has a setting for PostgreSQL where we can specify that manual vacuuming should be done after every sample … we currently have it disabled, I’m seeing if enabling it (and disabling auto vacuuming which can kick in at random times) will give us consistent performance while also keeping dead tuples under control (too many dead tuples slow down query performance)

** Already tested and Fixed in benchmark-runner Pod, case to huge improvement, need to fix it also in VM

  1. Removing effective_cache_size = 8192MB The default parameter is effective_cache_size = 4096MB, configure as Pod.