Go best practices, six years in

Re:Go best practices, six years in by pjungwir on Sunday May 01, 2016 @11:57PM (#11609129)

I'm looking to transition from Rails to something more performant. Phoenix is at the top of my list, but these benchmarks worry me:

https://www.techempower.com/benchmarks/#section=data-r12&hw=...

In both Phoenix has very high error rates, and in the first it seems really slow. Here is their Phoenix test app:

https://github.com/TechEmpower/FrameworkBenchmarks/tree/mast...

So what is going on there? Is it less of a perf win than I've heard? Is there something bad with their code?

[ Parent | on HN ]

Re:Go best practices, six years in by learc83 on Monday May 02, 2016 @02:50AM (#11609570)

Here's a reply from the creator. https://www.reddit.com/r/elixir/comments/48ke69/any_reason_w...

[ Parent | on HN ]

Re:Go best practices, six years in by brightball on Monday May 02, 2016 @06:47AM (#11610420)

Yea, I had the same concern until I heard the reason. There are other benchmarks out there that compare to Go/gin that are more accurate.

Edit: Here.

https://gist.github.com/omnibs/e5e72b31e6bd25caf39a

[ Parent | on HN ]

Re:Go best practices, six years in by jake_morrison on Monday May 02, 2016 @01:56AM (#11609424)

The benchmark for Phoenix was done at the last minute, and had a lot of problems which they didn't have opportunity to fix. The next round will be better.

[ Parent | on HN ]

Re:Go best practices, six years in by asdf1234 on Monday May 02, 2016 @09:14PM (#11617123)

There were problems with the benchmarks and nobody had time to fix them. This is usually the case when the benchmarks have high error rates and this has also happened in the past with Haskell, C# and F# libraries.

[ Parent | on HN ]