3 ms·

He's benchmarking the difference between a Pi2 and a server, so it makes no sense to introduce another variable - unoptimized, unfinished code.

• geerlingguy 11y ago
  As long as the code itself is the same... It's not a variable. I always benchmark against the same point release or git hash. It's nice to have comparisons of e.g. Beta 1 vs Beta 2, so I can find out where performance regressions are introduced into the code.
  • radicalbyte 11y ago
    The problem is the increased risk of nonsense benchmarks. I.e. if the unoptimized code is super slow because the naive implementation compiles to something unsuited to, say, the x86 microarchitecture. Or that performance is limited by lock contention. That's way more likely with pre-release then production-grate software. If you want to compare B1 and B2 that's great - but then you post to hackernews a comparison between two Drupal betas, not a comparison between two hardware platforms.
  • radicalbyte 11y ago
    Benchmarking beta software is of course great and very valuable - it focuses attention and will hopefully motivate projects to improve performance. It's just strange to do it in a piece which is predominantly arguing for the effectiveness of a cheap hardware solution :)