Beanbun

Beanbun 是用 PHP 编写的多进程网络爬虫框架,具有良好的开放性、高可扩展性,基于 Workerman。

Runssource: GitHubPHPMITcommit 092063908d58

PHP, MIT licensed. The project labels itself: beanbun, crawler, php and spider.

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

Beanbun 1.0.4 with vendored workerman and guzzle dependencies. PHP 8.3.6 extracted from apt. All source and vendor files parse without errors. Framework class instantiation, configuration, and all Helper methods (randUserAgent, formatUrl, getUrlByHtml) verified working.

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

At a glance

verdict
Runs
Argusic Score
93.5 / 100
cost of the verifying run
$0.30 (measured)
recorded runs
2
last tested
stars
1,258
forks
250
open issues
14
watchers
76
size
1 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 Beanbun, 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.

  • Composer not available (PHP built without phar extension, complex dep chain)8 minutes
  • PHP missing from container3 minutes
Install time
16 minutes
Cold machine to finish
16 minutes
Errors hit and fixed
2 hit, 2 fixed with no human help
How the result was proved
php8.3 test_beanbun.php exited 0, 25 passed 0 failed
Model tokens used
212,304
Exact commit tested
092063908d58
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.

========================================
exec
/bin/sh -lc 'echo "Start: 04:15"; date "+Current: %H:%M"' in /work/repo
 succeeded in 0ms:
Start: 04:15
Current: 04:31
exec
/bin/sh -lc "echo '{\"install_succeeded\": true, \"launch_succeeded\": true, \"install_minutes\": 1…
 succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 16, "errors": [{"msg": "PH…
tokens used
212,304

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 16 minutes.
  • Recovered from all 2 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 MIT, 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.

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/3Runs with mocks87.000.15
Argusic Runner1/3Runs100.000.30

Topics (from GitHub)

beanbuncrawlerphpspider

Embed the badge

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

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

Questions

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