| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Yoshimi Ichiyanagi <ichiyanagi(dot)yoshimi(at)lab(dot)ntt(dot)co(dot)jp> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, menjo(dot)takashi(at)lab(dot)ntt(dot)co(dot)jp, ishizaki(dot)teruaki(at)lab(dot)ntt(dot)co(dot)jp |
| Subject: | Re: [HACKERS][PATCH] Applying PMDK to WAL operations for persistent memory |
| Date: | 2018-01-17 20:29:11 |
| Message-ID: | CA+TgmobUrKBWgOa8x=mbW4Cmsb=NeV8Egf+RSLp7XiCAjHdmgw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jan 16, 2018 at 2:00 AM, Yoshimi Ichiyanagi
<ichiyanagi(dot)yoshimi(at)lab(dot)ntt(dot)co(dot)jp> wrote:
> Using pgbench which is a PostgreSQL general benchmark, the postgres server
> to which the patches is applied is about 5% faster than original server.
> And using my insert benchmark, it is up to 90% faster than original one.
> I will describe these details later.
Interesting. But your insert benchmark looks highly artificial... in
real life, you would not insert the same long static string 160
million times. Or if you did, you would use COPY or INSERT .. SELECT.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-01-17 20:31:22 | Re: PostgreSQL crashes with SIGSEGV |
| Previous Message | Peter Geoghegan | 2018-01-17 20:19:50 | Re: PostgreSQL crashes with SIGSEGV |