Sönke Ludwig

It seems like the `reusePort` property isn't handled correctly on OS X and thus only a single core is being used. I'll have a look at it.

Okay, `reusePort` now works on OS X, too. I've also tagged a new alpha release (0.8.2-alpha.3), can you re-run with a `dub upgrade --prerelease`?

BTW, increasing the number of threads above the number of logical cores (sometimes even physical cores) will usually degrade the performance somewhat. It can be useful to hide latencies introduced...

Do you see multiple "Listening for requests on http://127.0.0.1:8080/" messages now, or are there still any "Failed to listen on 127.0.0.1:8080" ones? I'll attempt to run an own benchmark on...

Okay, I can confirm the issue. Although I have a number of VMs running in parallel, it's clear that the performance is degrading in multi-threaded mode. There must be some...

I kind of missed its introduction to the code base, but it looks like using `Nullable!Json toRepresentation` and `@embedNullable` instead of `@optional` might be a way around this.

What I meat is something like this: ```D struct DNVal(T) { Kind kind; T value; Json toJson() const { return kind == Kind.is_null ? Json(null) : Json(value); } static DNVal...

Looks like CouchDB has a buggy HTTP/1.1 implementation. As a workaround, a way to force `Connection: close` in the request header of `RestInterfaceClient` requests is needed. Another fix, which I...

(But really, CouchDB should be fixed! This is a huge waste of bandwidth and latency)

This approach has a similar issue as #2308, where just a host name is accepted as a valid URL (which it isn't). In conjunction with the explicit default schema, it...