On Thu, 26 Dec 2013 12:01:24 GMT, David Nadlinger wrote:
Now, two questions:
1) Is there a comprehensive test suite I can run to ensure that there are no more miscompilations/… left in the basic structure? How can I easily run the unit test using dub (vibe.d being a library project)?
Pretty good coverage can be achieved by doing 2 steps:
1) Going throgh https://github.com/rejectedsoftware/vibe.d/tree/master/examples and running both dub run and dub run --build=unittest for each example to verify that common use patterns work as expected
2) Building whole vibe.d with dub --build=unittest to run all general unittests
There are also some high-level functional tests in https://github.com/rejectedsoftware/vibe.d/tree/master/tests but those don't get much attention right now
2) I recall seeing some promising performance numbers for vibe.d quite a while back, although I don't remember where exactly that was. Are there any benchmark implementations I could try to get some "interesting" numbers?
Most recent published benchmark of vibe.d usage was https://atilanevesoncode.wordpress.com/2013/12/05/go-vs-d-vs-erlang-vs-c-in-real-life-mqtt-broker-implementation-shootout/
AFAIK https://github.com/rejectedsoftware/vibe.d/tree/master/examples/bench-http-server and https://github.com/rejectedsoftware/vibe.d/tree/master/examples/bench-http-request are what Sonke himself has been using for quick tests.
My old stuff is here https://github.com/Dicebot/web-performance-tests but it was focused on comparing different implementations in one specific scenario, not comprehensive coverage of different load/processing patterns