| From: | Sameer Kumar <sameer(dot)kumar(at)ashnik(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, Abhijit Menon-Sen <ams(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
| Subject: | Re: [PATCH] Use MAP_HUGETLB where supported (v3) |
| Date: | 2013-11-17 04:22:11 |
| Message-ID: | CADp-Sm6v1YJkHEg-Xfob5Mkpyc0mPR=XHwcP459+QUQOR-DhOA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I was recently running some tests with huge page tables. I ran them on two
different architectures: x86 and PPC64.
I saw some discussion going on over here so thought of sharing.
I was using 3 Cores, 8GB RAM, 2 LUN for filesystem (1 for dbfiles and 1 for
logfiles) for these tests...
I had dedicated
(shared_buffers + 400bytes*max_connection + wal_buffers)/Pagesize [from
/proc/meminfo] for huge pages. I kept some overcommit_hugepages to be used
by work_mem (max_connection*work_mem)/Pagesize
x86_64 bit gave me a benefit of 2-5% for TPC-C workload( I scaled from 1 to
100 users). PPC64 which uses 16MB and 64MB did not give me any benefits in
fact the performance degraded as the concurrency of system increased.
my 2 cents, hope it helps.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2013-11-17 06:54:36 | Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review]) |
| Previous Message | Peter Geoghegan | 2013-11-17 04:15:50 | Re: Storing pg_stat_statements query texts externally, pg_stat_statements in core |