Round 13 is up:
dsissitka
terakilobyte
DianaOlympos
Tons of reasons for that. Keep in mind, the Phoenix code is not super optimised and will probably evolve for the next round.
Still some interesting things to see :
- Second on cloud Data updates… not bad for a first entry
- Latency in general is low and really consistent. That is really nice, it means that the latency is quite deterministic in prod.
- Not so bad results at all, especially for a first round.
Idea to boost results : As most of these test need Json serialisation, it may make sense to use :jiffy instead of Poison for Json serialisation. It is not that surprising to see it in production when you only deal with JSON answer or input and you want to get more power from your hardware.
0
OvermindDL1
josevalim
Creator of Elixir
Someone should definitely send a PR for that as I believe Poison is the one taking most time on the JSON results.
2
dwahyudi
Probably some of the Phoenix code there could be improved… but…
From the perspective of a Ruby on Rails guy like me, that Phoenix performance is stunning 
considering that it is a full stack web framework.
1
dsissitka
Are you talking about the JSON serialization test or all of the tests that return a JSON response?
I tried updating the data update and multiple query tests and it didn’t make a difference. I think that might be because we’re getting 1,915 and 1,945 requests per second there and Poison doesn’t have any trouble keeping up:
def test do
data = for _ <- 1..20 do
%{id: :rand.uniform(10_000), random_number: :rand.uniform(10_000)}
end
Benchee.run(%{time: 10}, %{
"jiffy" => fn -> :jiffy.encode(data) end,
"poison" => fn -> Poison.encode!(data) end
})
end
Erlang/OTP 19 [erts-8.1] [source-e7be63d] [64-bit] [smp:4:4] [async-threads:10] [hipe] [kernel-poll:false]
Compiling 1 file (.ex)
Interactive Elixir (1.3.3) - press Ctrl+C to exit (type h() ENTER for help)
iex(1)> Jsontest.test
Erlang/OTP 19 [erts-8.1] [source-e7be63d] [64-bit] [smp:4:4] [async-threads:10] [hipe] [kernel-poll:false]
Elixir 1.3.3
Benchmark suite executing with the following configuration:
warmup: 2.0s
time: 10.0s
parallel: 1
Estimated total run time: 24.0s
Benchmarking jiffy...
Benchmarking poison...
Name ips average deviation median
jiffy 38.51 K 25.97 μs ±81.62% 20.00 μs
poison 21.35 K 46.84 μs ±57.78% 37.00 μs
Comparison:
jiffy 38.51 K
poison 21.35 K - 1.80x slower
I tried updating the JSON serialization test to use jiffy but unfortunately my development environment can only manage 11,000 requests per second. 
0
PragTob
exactly… what throws me off with the techempower benchmarks is them apparently classifying it as “Micro” framework, does anyone know what that’s about?
2
thousandsofthem
brightball
I saw this other JSON library in the Elixir Weekly that claims to be faster than poison as well: GitHub - whitfin/tiny: A small, fast and fully compliant JSON parser in Elixir · GitHub
0