vibe.d benchmarks

[Ola Fosheim Grøstad via Digitalmars-d]

On Thursday, 31 December 2015 at 08:51:31 UTC, yawniek wrote:
> from a slightly more distant view you can thus argue that 50k 
> rps vs 150k rps basically just means that the framework will 
> most probably not be your bottle neck.

Go scores 0.5ms latency, vibe.d scores 14.7ms latency. That's a 
big difference that actually matters.

Dart + MongoDB also does very well in the multiple request tests. 
17300 requests versus Python + MySQL at 8800.

> none the less, getting ahead in the benchmarks would help to 
> attract people who are then pleasantly surprised how easy it is 
> to make full blown services with vibe.

It also matters for people who pick a framework. Although the 
benchmark isn't great as general benchmarks it says something 
about:

1. Whether you can stick to the framework even when you need 
better performance, which is why the overhead versus raw platform 
speed is interesting.

2. That the framework has been engineered using performance 
measurements.

It is more useful for writing dynamic web services with simple 
requests rather than regular web servers though.