csp
csp is a high performance reactive stream processing library, written in C++ and Python
Runssource: GitHubhomepagePythonApache-2.0commit 4247a8b581d5
Python, Apache-2.0 licensed. The project labels itself: cpp, python, reactive, reactive programming, stream processing and streaming.
csp runs. An Argusic agent installed it in 2.5 minutes and hit 6 errors on a clean machine with no GPU, and the whole session was recorded.
csp 0.19.1 installed from PyPI into a venv, ran the bid-ask spread example producing correct output, and 1600/1628 tests pass after installing tzdata, anywidget, and python-rapidjson
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.3 of 100 (the mean of this project's run scores).
At a glance
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.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Source build failed: missing python3-dev headers (Development.Embed component not found)5 minutes
- test_websocket.py collection error: missing python-rapidjson1 minute
- test_db.py failures: missing tzdata package1 minute
- test_dateframe::test_perspective failure: missing anywidget1 minute
- Source build failed: vcpkg dependency tree incomplete - arrow, parquet, thrift, librdkafka, gtest not fully installed
- test_examples.py collection error: examples directory not bundled in PyPI wheel
- Install time
- 3 minutes
- Cold machine to finish
- 38 minutes
- Errors hit and fixed
- 6 hit, 4 fixed with no human help
- How the result was proved
- csp.run example printed bid/ask/spread correctly; pytest ran 1600 passed, 26 skipped, 2 xfailed in 93.5s
- Model tokens used
- 225,046
- Exact commit tested
- 4247a8b581d5
- 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
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
2026-10-21 02:32:07.081129 ask:2.0 2026-10-21 02:32:07.081129 spread:1.0 SUCCESS: Application ran correctly Now I have all the data needed. Let me compile the final report. exec /bin/sh -lc 'cd /tmp && /tmp/venv/bin/python -m pytest /tmp/venv/lib/python3.12/site-packages/csp/t… succeeded in 94286ms: 1600 passed, 26 skipped, 2 xfailed, 611 warnings, 14 subtests passed in 93.50s (0:01:33) Now I have everything. Let me compile the final result. tokens used 225,046 Now I have everything. Let me compile the final result.
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 2.5 minutes, faster than the median of the 3 comparable projects Argusic has measured.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
What did not, or is not known
- Hit 6 errors during setup, 2 of which were not solved.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 4 cpp projects Argusic has installed and timed, csp was the 2nd fastest to reach a running state, and 3 of 4 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 2.5 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
Topics (from GitHub)
cpppythonreactivereactive-programmingstream-processingstreaming
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/csp)Questions
- Does csp run?
- Yes. csp runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 6 errors on the way, and recorded the session.
- How did Argusic test csp?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 4247a8b581d5. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test csp?
- The run that produced this verdict cost $0.46: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does csp take to install?
- 2.5 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 csp need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing csp?
- 6 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.
- How does csp compare with the alternatives?
- Of the 4 cpp projects Argusic has installed and timed, csp was the 2nd fastest to reach a running state, and 3 of 4 reached one at all.
- Where is the evidence for csp?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.