Re: Add min and max execute statement time in pg_stat_statement
От | Robert Haas |
---|---|
Тема | Re: Add min and max execute statement time in pg_stat_statement |
Дата | |
Msg-id | CA+TgmoZ_y5TEONDHQcFs2x83bEOBUDxr1ieqoVC3qyHFf2sE3Q@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Add min and max execute statement time in pg_stat_statement (KONDO Mitsumasa <kondo.mitsumasa@lab.ntt.co.jp>) |
Ответы |
Re: Add min and max execute statement time in pg_stat_statement
|
Список | pgsql-hackers |
On Wed, Jan 22, 2014 at 3:32 AM, KONDO Mitsumasa <kondo.mitsumasa@lab.ntt.co.jp> wrote: >> OK, Kondo, please demonstrate benchmarks that show we have <1% impact >> from this change. Otherwise we may need a config parameter to allow >> the calculation. > > OK, testing DBT-2 now. However, error range of benchmark might be 1% higher. > So I show you detail HTML results. To see any impact from spinlock contention, I think you're pretty much going to need a machine with >32 cores, I think, and lots of concurrency. pgbench -S is probably a better test than DBT-2, because it leaves out all the writing, so percentage-wise more time will be spent doing things like updating the pgss hash table. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: