Updated test logic and Updated Effinitive version to 2.1.3#853
Updated test logic and Updated Effinitive version to 2.1.3#853HBartosch wants to merge 10 commits into
Conversation
…rties initialization
…eadability and maintainability
…ting properties in ProcessedItem class
|
/benchmark -f effinitive |
|
👋 |
Benchmark ResultsFramework:
Full log |
|
/benchmark -f effinitive --save |
|
👋 |
|
|
|
/benchmark -f effinitive --save |
|
👋 |
Benchmark ResultsFramework:
Full log |
|
This is not how a static file works, you can't preload all files into an app managed heap snapshot and serve them. Also a lot of inconsistency and clearly blindly vibe coded logic in this file.. Please fix this or I have to move it into engine section. Comments in a framework source core with "// The benchmark sends "br;q=1, gzip;q=0.8" so br is explicitly preferred." are certainly not acceptable. |
|
Missed this in my review. Will keep an eye out for things like this thanks. |
|
Deprecated the packages to not use the packages for the new versions. will be reworking this section. Again. Really appreciate it! |
Description
Updated test logic and Updated Effinitive version to 2.1.1
PR Commands — comment on this PR to trigger (requires collaborator approval):
/benchmark -f <framework>/benchmark -f <framework> -t <test>/benchmark -f <framework> --saveAlways specify
-f <framework>. Results are automatically compared against the current leaderboard.Run benchmarks locally
You can validate and benchmark your framework locally with the lite script — no CPU pinning, fixed connection counts, all load generators run in Docker.
Requirements: Docker Engine on Linux. Load generators (gcannon, h2load, h2load-h3, wrk, ghz) are built as self-contained Docker images on first run.