On Tuesday, 23 September 2025 at 15:35:47 UTC, Dmitry Olshansky
wrote:
On Monday, 22 September 2025 at 11:14:17 UTC, Sönke Ludwig
Again, the "default" is a high-level issue and none of
vibe-core's business. The simplest way to have that work is to
use `HTTPServerOption.reusePort` and then start as many
processes as desired.
So I did just that. To my surprise it indeed speeds up all of
my D server examples.
That 15% speed was suspicious, so I looked closer into what I was
doing and indeed I was launching N+1 processes due to a bug in my
script. 9 / 8 ~ 1.15 so here goes.
The speed ups are roughly:
On vibe-http-light:
8 cores 1.14
12 cores 1.10
16 cores 1.08
24 cores 1.05
32 cores 1.06
48 cores 1.07
Proper numbers:
8 cores 1.01
12 cores 1.01
16 cores 1.02
24 cores 1.00
32 cores 1.02
48 cores 1.05
On plain photon-http:
8 cores 1.15
12 cores 1.10
16 cores 1.09
24 cores 1.05
32 cores 1.07
48 cores 1.04
Proper numbers:
8 cores 1.02
12 cores 1.02
16 cores 1.01
24 cores 1.02
32 cores 1.04
48 cores 1.02
So it *seems* there is still a little bit of gain, I'm
investigating where the benefit actually comes from, keeping in
mind that there is some noise in the benchmark itself.
Lastly, I have found opportunities to speed up vibe-http even
without switching to vibe-core-light. Will send PRs.
First one to go:
https://github.com/vibe-d/vibe-http/pull/65
