From 9f10e0390823e6530b14a5c2b8531254db81c5b6 Mon Sep 17 00:00:00 2001 From: sjg Date: Mon, 29 Oct 2012 04:09:23 -0700 Subject: [PATCH] --- performance/index.html | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/performance/index.html b/performance/index.html index 27cf472..2c49476 100644 --- a/performance/index.html +++ b/performance/index.html @@ -8,7 +8,7 @@

It is true that one of the original goals of the DragonFly BSD project was performance-oriented, the project sought to do SMP in more straightforward, compos-able, understandable and algorithmic-ally superior ways to the work being done in other operating system kernels. This results of this process have become staggeringly obvious with the 3.0 and 3.2 releases of DragonFly, which saw a significant amount of polishing and general scalability work, the culmination of which can be seen in the following graph.

-

The following graph charts the performance of the PostgreSQL 9.3 development version as of September 2012 on DragonFly BSD 3.0 and 3.2, FreeBSD 9.1, NetBSD 6.0 and Scientific Linux 6.2 running Linux kernel version 2.6.32. The tests were performed using system defaults on each platform with pgbench as the test client with a scaling factor of 800. The test system in question was a dual-socket Intel Xeon X5650 with 24GB RAM.

+

The following graph charts the performance of the PostgreSQL 9.3 development version as of late June 2012 on DragonFly BSD 3.0 and 3.2, FreeBSD 9.1, NetBSD 6.0 and Scientific Linux 6.2 running Linux kernel version 2.6.32. The tests were performed using system defaults on each platform with pgbench as the test client with a scaling factor of 800. The test system in question was a dual-socket Intel Xeon X5650 with 24GB RAM.

[[!template id=performance-scaling-postgresql.tmpl]] -- 1.7.7.2