Recently we added some extra validation tests:
TCP Fragmentation - Including https://github.com/uNetworking/uWebSockets/blob/master/tests/fragment_test.ts tests, taken from uWebSockets test suite, we also added query parameters to the requests used to match our baseline.
Upload - Added tests using chunked encoding.
Static - Validate whether the framework follows the disk - "changes to the contents of the root folder must be dynamically reflected during the server runtime"
Upcoming changes
As a result, after a full validation sweep #1285 68 frameworks are now failing. Failing frameworks will be disabled until they are fixed, with an exception - if the only failures stem from static validations, this test will be removed from the entry as this test is being moved to unscored state for Flagship/Emerging/Experimental categories in the h1 section.
Why is static test being moved to unscored? - Quite simple, there is no clear way to fairly benchmark this across so many languages and technologies and not every framework has a static file serve module, for those cases it would be unfair to exclude the framework from a scored tests, directly penalizing its composite score, and would also be unfair to allow implementing a custom file server in the benchmark itself as that would penalize those that actually have one.
Upload test will be revisioned too, currently it is saturated at 200 Gbit/s because of hardware limitations.
Recently we added some extra validation tests:
TCP Fragmentation - Including https://github.com/uNetworking/uWebSockets/blob/master/tests/fragment_test.ts tests, taken from uWebSockets test suite, we also added query parameters to the requests used to match our baseline.
Upload - Added tests using chunked encoding.
Static - Validate whether the framework follows the disk - "changes to the contents of the root folder must be dynamically reflected during the server runtime"
Upcoming changes
As a result, after a full validation sweep #1285 68 frameworks are now failing. Failing frameworks will be disabled until they are fixed, with an exception - if the only failures stem from static validations, this test will be removed from the entry as this test is being moved to unscored state for Flagship/Emerging/Experimental categories in the h1 section.
Why is static test being moved to unscored? - Quite simple, there is no clear way to fairly benchmark this across so many languages and technologies and not every framework has a static file serve module, for those cases it would be unfair to exclude the framework from a scored tests, directly penalizing its composite score, and would also be unfair to allow implementing a custom file server in the benchmark itself as that would penalize those that actually have one.
Upload test will be revisioned too, currently it is saturated at 200 Gbit/s because of hardware limitations.