9 ms·

Why do you say this like it is impressive? Postgresql will scale to 32 cores with a real workload, and has done so for a few years. Mysql performance still ta

Why do you say this like it is impressive? Postgresql will scale to 32 cores with a real workload, and has done so for a few years. Mysql performance still tanks at 8 cores. It is very unlikely that mysql will be able to match postgresql for this workload, much less outperform it "handily".

spudlyo 14y ago
Postgresql will scale to 32 cores with a real workload, and has done so for a few years. Mysql performance still tanks at 8 cores. Both of those statements are not accurate, but hey, what's it matter? Without benchmarks we're both talking out our ass anyway.
- moe 14y ago
  The postgres part of the statement is accurate; http://rhaas.blogspot.de/2012/04/did-i-say-32-cores-how-about-64.html http://rhaas.blogspot.de/2012/04/did-i-say-32-cores-how-abou...
  - spudlyo 14y ago
    No, it's not. The referenced article is talking about Postgres 9.2devel. Version 9.2 isn't out yet, and even if it was, it still wouldn't be true due to the clause "and has done so for a few years". The lock manager bottlenecks that stopped PG from using more than 60% of the cpu power on a 24 core box were discovered a little less than a year ago. http://rhaas.blogspot.com/2011/07/read-scaling-out-to-32-cores.html http://rhaas.blogspot.com/2011/07/read-scaling-out-to-32-cor...
    - papsosouid 14y ago
      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...
      - spudlyo 14y ago
        Your MySQL example isn't exactly relevant. It was in 2007, yet you said "MySQL still tanks at 8 cores". Furthermore it was on FreeBSD, with a flawed libpthread. In terms of "real" workloads, I'm not going to bother getting into it, as this is quickly devolving in to a true Scotsman argument. Instead of arguing pointlessly about it, maybe our energy would be better spent publishing some benchmarks.
      - deleted 14y ago
        [deleted]

spudlyo 14y ago

Postgresql will scale to 32 cores with a real workload, and has done so for a few years. Mysql performance still tanks at 8 cores. Both of those statements are not accurate, but hey, what's it matter? Without benchmarks we're both talking out our ass anyway.

moe 14y ago
The postgres part of the statement is accurate; http://rhaas.blogspot.de/2012/04/did-i-say-32-cores-how-about-64.html http://rhaas.blogspot.de/2012/04/did-i-say-32-cores-how-abou...
- spudlyo 14y ago
  No, it's not. The referenced article is talking about Postgres 9.2devel. Version 9.2 isn't out yet, and even if it was, it still wouldn't be true due to the clause "and has done so for a few years". The lock manager bottlenecks that stopped PG from using more than 60% of the cpu power on a 24 core box were discovered a little less than a year ago. http://rhaas.blogspot.com/2011/07/read-scaling-out-to-32-cores.html http://rhaas.blogspot.com/2011/07/read-scaling-out-to-32-cor...
  - papsosouid 14y ago
    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...
    - spudlyo 14y ago
      Your MySQL example isn't exactly relevant. It was in 2007, yet you said "MySQL still tanks at 8 cores". Furthermore it was on FreeBSD, with a flawed libpthread. In terms of "real" workloads, I'm not going to bother getting into it, as this is quickly devolving in to a true Scotsman argument. Instead of arguing pointlessly about it, maybe our energy would be better spent publishing some benchmarks.
    - deleted 14y ago
      [deleted]