FrameworkBenchmarks icon indicating copy to clipboard operation
FrameworkBenchmarks copied to clipboard

Source for the TechEmpower Framework Benchmarks project

Results 320 FrameworkBenchmarks issues
Sort by recently updated
recently updated
newest added

In modern applications, especially in microservice architectures, outgoing REST calls play a critical role in communication with external APIs and services. While the current test suite covers many scenarios, there...

Actually a lot of devs say that this bench is too synthetic !! Almost all benchs are so. Is it a question for the all devs helping with this benchmark...

This is a port of the httpaf implementation found [here](https://github.com/TechEmpower/FrameworkBenchmarks/blob/master/frameworks/OCaml/httpaf/httpaf_unix.ml) to use the maintained fork httpun and also try out the new multicore concurrency library eio. Not performing as well...

[feat: add --force-rm flag to configure removing intermediate docker layers](https://github.com/TechEmpower/FrameworkBenchmarks/commit/15c254722862df4089ff8210d5f41d7874ec6c7a) This commit makes it possible to turn off the removal of intermediate docker layers when building the tfb containers by...

- move the server header to the router and add it to all responses. - move the response boxing to the router simplifying the return types of each handler. https://github.com/hyperium/http-body/pull/150...

Please, no more http: length hard encoded. No more template response cache !!! The template is OK to cache, but the response for the fortunes is NOT OK. https://github.com/TechEmpower/FrameworkBenchmarks/pull/9560#issuecomment-2607279905

Currently the test runner intentionally removes each layer unconditionally in a docker file. https://github.com/TechEmpower/FrameworkBenchmarks/blob/b9f7af61769d62058acc9fe493b0f549ad3293ad/toolset/utils/docker_helper.py#L42 This prevents using the layers for caching build output of deps. E.g. in a Rust docker...

According to https://github.com/TechEmpower/FrameworkBenchmarks/issues/8420 test mutations should be limited. > The number of test mutations will be limited to 10. ~This change makes mutations fail for frameworks if the maximum is...

_I've opened this PR because it is a point of frustration when implementing tests for new frameworks, but I've marked it as draft because the change may be too breaking._...