Re: Allow a per-tablespace effective_io_concurrency setting
| От | Josh Berkus |
|---|---|
| Тема | Re: Allow a per-tablespace effective_io_concurrency setting |
| Дата | |
| Msg-id | 55E76AB7.4030306@agliodbs.com обсуждение исходный текст |
| Ответ на | Re: [PERFORM] intel s3500 -- hot stuff (Julien Rouhaud <julien.rouhaud@dalibo.com>) |
| Ответы |
Re: Allow a per-tablespace effective_io_concurrency setting
Re: Allow a per-tablespace effective_io_concurrency setting Re: Allow a per-tablespace effective_io_concurrency setting |
| Список | pgsql-hackers |
On 09/02/2015 02:25 PM, Tomas Vondra wrote: > > As I explained, spindles have very little to do with it - you need > multiple I/O requests per device, to get the benefit. Sure, the DBAs > should know how many spindles they have and should be able to determine > optimal IO depth. But we actually say this in the docs: My experience with performance tuning is that values above 3 have no real effect on how queries are executed. -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com
В списке pgsql-hackers по дате отправления: