Repository navigation
[anole] v0.5.0 - #1692
[anole] v0.5.0#1692
Conversation
|
@MDA2AV I'm building bindings for Anole's C ABI that run existing Fastify and FastAPI apps on Anole's engine as a drop-in server: the app's code stays the same, and only the server underneath changes. Would it be okay to add them here as entries (for example |
|
/benchmark -f anole |
|
👋 Benchmark request received. A collaborator will review and approve the run. |
Benchmark ResultsFramework:
Composite score, main against this run, in the board's default view:
The results on main were measured in another session, so a few points up or down can be the machine and not the change. Full log |
|
/benchmark -f anole --save |
|
👋 Benchmark request received. A collaborator will review and approve the run. |
Sure but it still needs to be marked as experimental |
Benchmark ResultsFramework:
Composite score, main against this run, in the board's default view:
The results on main were measured in another session, so a few points up or down can be the machine and not the change. Full log |
|
@MDA2AV will do, thanks! |
This moves the anole entry from v0.1.2 to v0.5.0 (pinned by commit eb3650ec). The entry's code is unchanged: only the pin in build.zig.zon. It's still standard mode with default settings, and the new behaviour all lands as library defaults, with no benchmark-only options.
What changed for the profiles the entry runs: