benchmark doesn't verify response

[amichair]

If you don't verify that the server response is correct, it's not clear what's being benchmarked...

Currently the server can return anything, including an error code, and the benchmark continues smoothly.

The response doesn't need to be verified for each request, but at least once before the benchmark begins, just to make sure you're comparing apples to apples.

[orangy]

This is not something I maintain, it was a temporary project to check how everything works. I suggest using TechEmpower Benchmarks for real data.

[amichair]

I see. Then you should write that in bold at the top of the project readme...

[orangy]

I'm sorry, but why should I? That's my personal repo, it's not something I sell or associate with the company I work for. I think assumptions should be the other way around :)

[amichair]

I didn't imply this has to be related to your day job... I have no idea what you do for a living.

But you do have a welcoming readme, with instructions, attributions, a Contributing section... that kind of sends the message that it's aimed at developers other than yourself, and is a project that welcomes others to use it and contribute to it. After they (I?) take the time to do it (granted, not knowing if anything will be merged), it's strange to be told it's just a private project that does not accept feedback or contribution.

But sure, it's up to you. And thanks for putting this up, it's actually useful - TechEmpower don't have things like bytes of garbage generated per request which is a useful statistic for some, nor do they have all of the servers/frameworks that you do.