mirrors/zap
1
0
Fork 0
mirror of https://github.com/zigzap/zap.git synced 2025-10-20 23:24:09 +00:00
Code Activity

fix typo in README.

Browse source
This commit is contained in:
renerocksai 2025-03-30 20:03:15 +02:00
parent 3a2246ba50
commit 44ac2f2c3a
No known key found for this signature in database
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
README.md
View file

@ -177,12 +177,12 @@ claim any performance fame for itself. In this initial implementation of Zap,
I didn't care about optimizations at all.
But, how fast is it? Being blazingly fast is relative. When compared with a
simple GO HTTP server, a simple Zig Zap HTTP server performed really good on my
simple GO HTTP server, a simple Zig Zap HTTP server performed really well on my
machine (x86_64-linux):
- Zig Zap was nearly 30% faster than GO
- Zig Zap had over 50% more throughput than GO
- **YMMV !!!**
- **YMMV!!!**
So, being somewhere in the ballpark of basic GO performance, zig zap seems to be
... of reasonable performance 😎.
@ -190,7 +190,7 @@ So, being somewhere in the ballpark of basic GO performance, zig zap seems to be
I can rest my case that developing ZAP was a good idea because it's faster than
both alternatives: a) staying with Python, and b) creating a GO + Zig hybrid.
### On (now missing) Micro-Benchmakrs
### On (now missing) Micro-Benchmarks
I used to have some micro-benchmarks in this repo, showing that Zap beat all the
other things I tried, and eventually got tired of the meaningless discussions