mirror of
https://github.com/zigzap/zap.git
synced 2025-10-20 15:14:08 +00:00
49f5cd9342
In the 0.12.0 branch, [httpz](https://github.com/karlseguin/http.zig) was added to the perf measurements. Apparently, somehow this got lost, which is a pity. httpz is super-promising. Given the perf benchmarks in [this PR comment](https://github.com/antonputra/tutorials/pull/280#issuecomment-2362637299), I would have expected httpz to be on par with or better than zap in our `measure.sh` tests. However, on my M3 max mac box, I get the following: **ZAP**: ``` ➜ zap git:(reintroduce_httpz_perf) ✗ ./wrk/measure.sh zig-zap INFO: Listening on port 3000 Listening on 0.0.0.0:3000 INFO: Server is running 4 workers X 4 threads with facil.io 0.7.4 (kqueue) * Detected capacity: 131056 open file limit * Root pid: 73099 * Press ^C to stop INFO: 73110 is running. INFO: 73111 is running. INFO: 73112 is running. INFO: 73113 is running. ======================================================================== zig-zap ======================================================================== Running 10s test @ http://127.0.0.1:3000 4 threads and 400 connections Thread Stats Avg Stdev Max +/- Stdev Latency 1.31ms 533.41us 18.77ms 90.57% Req/Sec 76.67k 9.04k 86.46k 84.25% Latency Distribution 50% 1.15ms 75% 1.17ms 90% 1.75ms 99% 2.94ms 3052064 requests in 10.02s, 462.80MB read Socket errors: connect 0, read 135, write 0, timeout 0 Requests/sec: 304601.19 Transfer/sec: 46.19MB ``` **httpz**: ``` ➜ zap git:(reintroduce_httpz_perf) ✗ ./wrk/measure.sh httpz ======================================================================== httpz ======================================================================== Running 10s test @ http://127.0.0.1:3000 4 threads and 400 connections Thread Stats Avg Stdev Max +/- Stdev Latency 2.26ms 528.72us 18.84ms 84.61% Req/Sec 44.46k 7.35k 85.50k 88.00% Latency Distribution 50% 2.35ms 75% 2.39ms 90% 2.43ms 99% 3.26ms 1768925 requests in 10.01s, 91.10MB read Socket errors: connect 0, read 230, write 0, timeout 0 Requests/sec: 176712.50 Transfer/sec: 9.10MB ``` Which looks way off. I must admit, I might have done a bad httpz implementation. Seeking help from @karlseguin. My motivation: route people away from zap to alternatives like httpz or even zzz, as those are pure zig, and seem to be of really good performance. I want a world in which we don't have to resort to C frameworks to do good, zig-worthy servers 😄 to come true.
39 lines
1.5 KiB
Zig
39 lines
1.5 KiB
Zig
.{
|
|
// This is the default name used by packages depending on this one. For
|
|
// example, when a user runs `zig fetch --save <url>`, this field is used
|
|
// as the key in the `dependencies` table. Although the user can choose a
|
|
// different name, most users will stick with this provided value.
|
|
//
|
|
// It is redundant to include "zig" in this name because it is already
|
|
// within the Zig package namespace.
|
|
.name = "httpz",
|
|
|
|
// This is a [Semantic Version](https://semver.org/).
|
|
// In a future version of Zig it will be used for package deduplication.
|
|
.version = "0.0.0",
|
|
|
|
// This field is optional.
|
|
// This is currently advisory only; Zig does not yet do anything
|
|
// with this value.
|
|
//.minimum_zig_version = "0.11.0",
|
|
|
|
// This field is optional.
|
|
// Each dependency must either provide a `url` and `hash`, or a `path`.
|
|
// `zig build --fetch` can be used to fetch all dependencies of a package, recursively.
|
|
// Once all dependencies are fetched, `zig build` no longer requires
|
|
// internet connectivity.
|
|
.dependencies = .{
|
|
.httpz = .{
|
|
.url = "git+https://github.com/karlseguin/http.zig?ref=master#ffdce2eeb8499c0b5001f5c5bf141cc33c22b215",
|
|
.hash = "12209018285fde7ae6216acafe44fc199036239e1f24bda2b513bbcc1b6bc9a70752",
|
|
},
|
|
},
|
|
.paths = .{
|
|
"build.zig",
|
|
"build.zig.zon",
|
|
"src",
|
|
// For example...
|
|
//"LICENSE",
|
|
//"README.md",
|
|
},
|
|
}
|