Skip to content

High I/O disk from postgres stats collector process

Currently, our runbot is consuming I/O disk from postgres stats collector process:

  • screen shot 2018-06-27 at 12 01 40

The instances used for the big-image are semi non-durability type since that is not used for a production environment (just testing).

Then we could change the postgresql configuration (for all versions) in order to reduce the I/O disk.

Maybe, reducing autovacuum process too.

Offtopic other process consuming I/O disk is:

  • screen shot 2018-06-28 at 14 08 57

I don't know if it is related with the postgres stats collector process