libhv

🔥 比libevent/libuv/asio更易用的网络库。A c/c++ network library for developing TCP/UDP/SSL/HTTP/WebSocket/MQTT/Redis client/server.

Runssource: GitHubhomepageCBSD-3-Clausecommit 62f1292b5735

C, BSD-3-Clause licensed. The project labels itself: curl, epoll, http client, http server, https, iocp, kcp and mqtt.

libhv runs. An Argusic agent installed it in 4 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

libhv 1.3.4 builds and installs; shared library (libhv.so) and static library (libhv.a) produced; httpd server serves HTTP/1.1 on port 8080/18080 responding to /ping with 200 OK; all 19 unit test binaries and integration benchmark pass cleanly.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.03 (measured)
recorded runs
2
last tested
stars
7,577
forks
1,373
open issues
66
watchers
134
size
7 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Install time
4 minutes
Cold machine to finish
4 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
bash scripts/unittest.sh exited 0 with all 19 test binaries passing; bash scripts/check.sh ran 493K HTTP requests with 100% success; bin/curl -v localhost:18080/ping returned HTTP 200 with body 'pong'
Model tokens used
111,325
Exact commit tested
62f1292b5735
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

Watch the session

The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.

A recording of attempt 2, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

Everything works perfectly out of the box. No errors or fixes needed. Here's the summary:
**Build**: `./configure` + `make` completed, producing `libhv.so`/`libhv.a` and 28 example binaries.
**Tests** (`scripts/unittest.sh`): all 19 test binaries passed — rbtree, hbase, date, ifconfig, mkd…
**Integration** (`scripts/check.sh`): `httpd` server launched, `curl /ping` returned `HTTP/1.1 200 …
httpd version: `1.26.11.5`.
tokens used
111,325
Everything works perfectly out of the box. No errors or fixes needed. Here's the summary:
**Build**: `./configure` + `make` completed, producing `libhv.so`/`libhv.a` and 28 example binaries.
**Tests** (`scripts/unittest.sh`): all 19 test binaries passed — rbtree, hbase, date, ifconfig, mkd…
**Integration** (`scripts/check.sh`): `httpd` server launched, `curl /ping` returned `HTTP/1.1 200 …
httpd version: `1.26.11.5`.

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Reached a running state on a clean machine, with the session recorded.
  • Installed in 4 minutes, faster than the median of the 5 comparable projects Argusic has measured.
  • Nothing broke on the way: zero errors between clone and running.
  • Ran without a GPU, so it does not need one to start.
  • Licensed BSD-3-Clause, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

Of the 6 curl projects Argusic has installed and timed, libhv was the 2nd fastest to reach a running state, and 6 of 6 reached one at all.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.
  • A quick evaluation: it was running 4 minutes after the clone.
  • Following its own README: the documented path worked with nothing to fix.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.03
Argusic Runner1/3Runs100.000.03

Topics (from GitHub)

curlepollhttp-clienthttp-serverhttpsiocpkcpmqttopensslredisrequestswebserverwebsocketwebsocket-clientwebsocket-serverwrk

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/libhv.svg)](https://argusic.com/subject/libhv)

Questions

Does libhv run?
Yes. libhv runs. Argusic installed and launched it on a clean machine in 4 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test libhv?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 62f1292b5735. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test libhv?
The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does libhv take to install?
4 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does libhv need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing libhv?
Nothing did, in the recorded run: zero errors between clone and running.
How does libhv compare with the alternatives?
Of the 6 curl projects Argusic has installed and timed, libhv was the 2nd fastest to reach a running state, and 6 of 6 reached one at all.
Where is the evidence for libhv?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion