You are making assumptions about one scenario based on limitations encountered in a very different scenario. The problems that occur around 24 cores occur on b

You are making assumptions about one scenario based on limitations encountered in a very different scenario. The problems that occur around 24 cores occur on benchmarks consisting entirely of select statements against a single table. As I said, postgresql has scaled to 32 cores for real workloads for a few years. Real workloads have more than one table. See here for an example of mysql having problems at only 8 cores (and postgresql destroying mysql's performance): http://www.scribd.com/doc/551889/Introducing-Freebsd-70 http://www.scribd.com/doc/551889/Introducing-Freebsd-70 Postgresql scaling to 28 cores in 2007: https://docs.google.com/viewer?a=v&q=cache:-ytn3fY_Lr8J:www.pgcon.org/2007/schedule/attachments/22-Scaling%2520PostgreSQL%2520on%2520SMP%2520Architectures%2520--%2520An%2520Update+postgresql+32+cpu&hl=en&gl=ca&pid=bl&srcid=ADGEESixa00UkghJF8p1l9rfkwt56Cf4E3ZJHXSm3DIAciCB-7jEOc9LWWfyq9RXBb81JdCim3MxSV3RnVav7UnJuv8Oap4xspQBak9_DmWXT7t3kZjA9t-TB_HG96eVsyn-P5blyize&sig=AHIEtbRAXnaktHnXerUe-LXHJL86KxBtOw https://docs.google.com/viewer?a=v&q=cache:-ytn3fY_Lr8J:... Postgresql on 32 core t2000 being able to scale up to 1024 concurrent clients in 2008: http://www.pgcon.org/2008/schedule/attachments/50_46_pgcon2008_problem.pdf http://www.pgcon.org/2008/schedule/attachments/50_46_pgcon20...