tengine

A high-performance web server and reverse proxy, 100% compatible with nginx.

Runssource: GitHubhomepageCBSD-2-Clausecommit f9c9f759c029

C, BSD-2-Clause licensed. The project labels itself: forward proxy, health check, http3, kubernetes ingress, load balancer, lua, nginx and quic.

tengine runs. An Argusic agent installed it in 3.3 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Tengine 3.2.0 is built from source, installed under /work/repo/build-install, runs as a HTTP server on port 8080 answering 200 OK, and passes the nginx-tests and tengine-tests test suites (554 total assertions across 22 test files, all pass).

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 96 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
96 / 100
cost of the verifying run
$0.07 (measured)
recorded runs
2
last tested
stars
13,430
forks
2,508
open issues
513
watchers
867
size
26 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.

Time lost to each failure while testing tengine, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • PCRE library not found at configure time2 minutes
  • zlib library not found at configure time0.5 minutes
  • Permission denied installing to /usr/local/tengine (no root)0.5 minutes
  • Permission denied binding to port 800.3 minutes
Install time
3 minutes
Cold machine to finish
13 minutes
Errors hit and fixed
4 hit, 4 fixed with no human help
How the result was proved
curl -s -o /dev/null -w 'HTTP Status: %{http_code}, Body bytes: %{size_download}' http://localhost:8080/ returned 'HTTP Status: 200, Body bytes: 641'; prove ran 22 test files across both test directories (nginx-tests/ and tengine-tests/) all passing
Model tokens used
128,774
Exact commit tested
f9c9f759c029
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 1, 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.

 succeeded in 0ms:
done
exec
/bin/sh -lc 'date +%s' in /work/repo
 succeeded in 0ms:
1790580822
All done. Here's the final summary:
The project is **Tengine 3.2.0** (nginx-based web server). On this Ubuntu 24.04 container without r…
tokens used
128,774
All done. Here's the final summary:
The project is **Tengine 3.2.0** (nginx-based web server). On this Ubuntu 24.04 container without r…

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 3.3 minutes.
  • Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Ran without a GPU, so it does not need one to start.
  • Licensed BSD-2-Clause, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

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 3.3 minutes after the clone.

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/3Runs92.000.07
Argusic Runner1/3Runs100.000.07

Topics (from GitHub)

forward-proxyhealth-checkhttp3kubernetes-ingressload-balancerluanginxquicreverse-proxysm2tcp-proxytenginetlcptlsweb-server

Embed the badge

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

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

Questions

Does tengine run?
Yes. tengine runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 4 errors on the way, and recorded the session.
How did Argusic test tengine?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit f9c9f759c029. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test tengine?
The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does tengine take to install?
3.3 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 tengine need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing tengine?
4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for tengine?
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