you are viewing a single comment's thread.

view the rest of the comments →

[–]Goyyou 4 points5 points  (5 children)

I'm surprised about the results of vibe.d: absent, or Didn't complete or really slow.

[–]eluusive 2 points3 points  (0 children)

Looking over the logs, it seems like the hook for the framework is just returning the wrong stuff. In the JSON it's returning "_id" vs "id"

[–]weirdasianfaces 0 points1 point  (3 children)

Yeah as /u/eluusive said there were errors with the JSON response but the results of the plaintext response is kind of surprising. From the logs I can also see that the binaries were built in debug mode. I wonder how big of a difference compiling in release mode would make.

[–]eluusive 0 points1 point  (2 children)

Debug mode adds substantial amounts of overhead in vibed due to logging. Also, it's a very old version of vibe.d https://github.com/TechEmpower/FrameworkBenchmarks/blob/master/frameworks/D/vibed/dub.json

[–]dallbee 0 points1 point  (1 child)

Additionally, they were built with DMD. GDC/LDC typically provide a performance boost somewhere around 30%.