| From: | Don Seiler <don(at)seiler(dot)us> |
|---|---|
| To: | pgsql-performance(at)lists(dot)postgresql(dot)org |
| Subject: | Setting effective_io_concurrency in VM? |
| Date: | 2017-11-27 18:23:46 |
| Message-ID: | CAHJZqBCAQYq46jdfNkJpaJ1SzeGnCjDnsMnGEod-_s7dEYGzow@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Good afternoon.
We run Postgres (currently 9.2, upgrading to 9.6 shortly) in VMWare ESX
machines. We currently have effective_io_concurrency set to the default of
1. I'm told that the data volume is a RAID 6 with 14 data drives and 2
parity drives. I know that RAID10 is recommended, just working with what
I've inherited for now (storage is high-end HP 3Par and HP recommended RAID
6 for best performance).
Anyway, I'm wondering if, in a virtualized environment with a VM datastore,
it makes sense to set effective_io_concurrency closer to the number of data
drives?
I'd also be interested in hearing how others have configured their
PostgreSQL instances for VMs (if there's anything special to think about).
Don.
--
Don Seiler
www.seiler.us
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2017-11-27 18:40:19 | Re: Setting effective_io_concurrency in VM? |
| Previous Message | Laurenz Albe | 2017-11-27 18:18:33 | Re: Half billion records in one table? RDS |