Hi,
Thanks a lot to both of you for the quick responses.
On Thu, 26 Dec 2013 15:21:29 GMT, Sönke Ludwig wrote:
With GIT master of DUB, "dub test" should work. For older versions there is a special "unittest" configuration ("dub --config=unittest --build=unittest").
The unit tests are not really suited for testing I/O and fiber related things, but the benchmark examples should normally be sufficiently complex to catch most issues there. For template/CTFE/linker stress testing, the vibed.org and code.dlang.org websites are also living quite on the cutting edge (at least for DMD).
I had a look at the vibe.d unit tests, the examples and the vibed.org/code.dlang.org repos. With LDC from the merge-2.064 branch they should now all build, and the few I actually tested seem to work.
What I used was "weighttp" on two separate linux machines connected by GbE. The client machine had to have a powerful CPU or "weighttp" wasn't able to saturate the "bench-http-server". Currently it's a little unclear how well the performance actually is, as it hasn't been benchmarked for a while and there were some changes in critical parts that may have had an influence. There is also a recent thread about this.
Hm, I don't think I'll be able to set up two locally connected, beefy enough machines until the holidays are over. Just using the benchmark server/client examples, it seems that the CPU overhead is a little lower than with the DMD-compiled executables, but that's obviously not a very good way of measuring things.
David