Tone the text down a bit

diff --git a/performance/index.html b/performance/index.html
index 967c2ad..29a1658 100644 (file)
--- a/performance/index.html
+++ b/performance/index.html
@@ -14,8 +14,9 @@
 
 <p>NetBSD 6.0 was unable to complete the benchmark run.</p>
 
 
 <p>NetBSD 6.0 was unable to complete the benchmark run.</p>
 

-<p>In this particular test, which other operating systems have often utilized to show how well they scale you can see that the scalability of DragonFly BSD 3.2 is nothing short of excellent. The scalability far surpasses other BSD-derived codebases and is roughly on par with the Linux kernel. DragonFly performs better than linux at lower concurrencies and the small performance hit at high client counts was given up willingly to retain the trademark interactivity that make BSD systems a pleasure to use.</p>
+<p>In this particular test, which other operating systems have often utilized to show how well they scale, you can see the immense improvement in scalability of DragonFly BSD 3.2. PostgreSQL's scalability in 3.2 far surpasses other BSD-derived codebases and is roughly on par with the Linux kernel (which has been the object of expensive, multi-year optimization efforts). DragonFly performs better than linux at lower concurrencies and the small performance hit at high client counts was given up willingly to ensure that we maintain acceptable interactivity even at extremely high throughput levels.</p>

 
 

+<p><em>Note: single-host pgbench runs like the ones above are not directly useful for estimating PostgreSQL scaling behavior. For example, any real-world setup that needs to handle that many transactions would be using multiple PostgreSQL servers and the client themselves would be running on a set of different hosts. This would be much less demanding of the underlying OS. If you plan to use PostgreSQL on DragonFly and are targeting high-throughput, we encourage you to do your own testing and would appreciate any reports of inadequate performance. That said, the above workload does demonstrate the effect of algorithmic improvements that have been incorporated into the 3.2 kernel and should positively affect many  real-world setups (not just PostgreSQL ones).</em></p>

 <br/>
 
 <h2>Swapcache</h2>
 <br/>
 
 <h2>Swapcache</h2>