On 05/09/2011 05:59 PM, Kevin Grittner wrote:
I'm going to pursue this digression just a little further, because it probably will be biting you sooner or later. We make sure to configure the BIOS on our database servers to turn off hyperthreading. It really can make a big difference in performance.
You're using connection pooling quite aggressively though. The sort of people who do actually benefit from hyperthreading are the ones who don't, where there's lots of CPU time being burnt up in overhead you don't see, and that even a virtual HT processor can help handle. I'm not a big fan of the current hyperthreading implementation, but it's not nearly as bad as the older ones, and there are situations where it is useful. I am unsurprised you don't ever see them on your workload though, you're well tweaked enough to probably be memory or disk limited much of the time.
-- Greg Smith 2ndQuadrant US greg@xxxxxxxxxxxxxxx Baltimore, MD PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.us "PostgreSQL 9.0 High Performance": http://www.2ndQuadrant.com/books -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
