SYSV shared memory vs mmap performance
Francois Tigeot <ftigeot@wolfpond.org>
From: Francois Tigeot <ftigeot@wolfpond.org>
To: pgsql-hackers@postgresql.org
Cc: kernel@dragonflybsd.org, tech-kern@NetBSD.org
Date: 2012-09-13T06:30:03Z
Lists: pgsql-hackers
Attachments
- Pg-benchmarks.2012-09.Sysv_shm.vs.mmap.pdf (application/pdf)
Hi, Given the recent decision to switch from SYSV shared memory to mmap and the concerns which were made with regard to performance on *BSD kernels, I've run a few Pgbench tests on a spare Xeon box. I tested PostgreSQL-9.3 from June 28th, as of commits: - c5b3451a8e72cb7825933d4f4827f467cb38b498 (mmap) - 5d594b73d988b1ac78c49d8a84deae6bae876d01 (sysv shared memory) I also used both Scientific Linux-6.2 and DragonFly BSD-3.1; the results are in the attached PDF document. To cut a long story short, Linux doesn't show any difference and DragonFly sees some heavy degradation under load. After a while, it starts swapping and performance goes to hell. The only *BSD system tested was DragonFly but I know from previous pgbench tests FreeBSD and NetBSD follow a similar performance curve The famous kern.ipc.shm_use_phys sysctl was set to 1, which is the default setting. -- Francois Tigeot
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Add missing space in event_source GUC description.
- c5b3451a8e72 9.3.0 cited