Re: [HACKERS] Patch: Write Amplification Reduction Method (WARM)
От | Mithun Cy |
---|---|
Тема | Re: [HACKERS] Patch: Write Amplification Reduction Method (WARM) |
Дата | |
Msg-id | CAD__OujziDQFR_NhRzAkXkOcR7ePf3BKwO9DOAwpOVF9sxwZbg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [HACKERS] Patch: Write Amplification Reduction Method (WARM) (Pavan Deolasee <pavan.deolasee@gmail.com>) |
Ответы |
Re: [HACKERS] Patch: Write Amplification Reduction Method (WARM)
|
Список | pgsql-hackers |
On Wed, Mar 22, 2017 at 3:44 PM, Pavan Deolasee <pavan.deolasee@gmail.com> wrote: > > This looks quite weird to me. Obviously these numbers are completely > non-comparable. Even the time for VACUUM FULL goes up with every run. > > May be we can blame it on AWS instance completely, but the pattern in your > tests looks very similar where the number slowly and steadily keeps going > up. If you do complete retest but run v18/v19 first and then run master, may > be we'll see a complete opposite picture? > For those tests I have done tests in the order --- <Master, patch18, patch18, Master> both the time numbers were same. One different thing I did was I was deleting the data directory between tests and creating the database from scratch. Unfortunately the machine I tested this is not available. I will test same with v19 once I get the machine and report you back. -- Thanks and Regards Mithun C Y EnterpriseDB: http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: