quill

Ultra-low-latency asynchronous C++17 logging and metrics library for performance-critical applications

Runssource: GitHubhomepageC++MITcommit 6fcd9c01d303

C++, MIT licensed. The project labels itself: async, asynchronous, cpp, cpp logging, cpp17, cpp20, cross platform and fmtlib.

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

442 unit and integration tests pass on Ubuntu with GCC 13.3.0, covering bounded/unbounded queues, backend worker, logging macros, std library type formatting, sinks, metrics, thread safety, timestamp ordering, and user-defined types.

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.02 (measured)
recorded runs
1
last tested
stars
3,044
forks
275
open issues
9
watchers
39
size
12 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
3 minutes
Cold machine to finish
7 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
cd /work/repo/build && ctest --output-on-failure -j4: 100% tests passed, 0 tests failed out of 442, total test time 31.80 sec
Model tokens used
27,000
Exact commit tested
6fcd9c01d303
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.

    'install_minutes': 2.5,
    'errors': [],
    'test_depth': 'tier1_real',
    'notes': 'Built and ran the full test suite for the Quill C++17 async logging library. No third…
    'verified_how': 'cd /work/repo/build && ctest --output-on-failure -j4: 100% tests passed, 0 tes…
    'final_state': '442 unit and integration tests pass on Ubuntu with GCC 13.3.0, covering bounded…
}
print('ARGUSIC_RESULT:' + json.dumps(result))
\"" in /work/repo
 succeeded in 0ms:
tokens used
27,000

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.
  • Nothing broke on the way: zero errors between clone and running.
  • Ran without a GPU, so it does not need one to start.
  • Licensed MIT, as reported by its host.

What did not, or is not known

  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

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.
  • 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.

  • skywalking verified to run · Java · 4 shared topics
  • vector verified to run · Rust · 3 shared topics
  • VictoriaMetrics verified to run · Go · 3 shared topics
  • thanos verified to run · Go · 3 shared topics
  • fluent-bit verified to run · C · 3 shared topics
  • coroot verified to run · Go · 3 shared topics

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs100.000.02

Topics (from GitHub)

asyncasynchronouscppcpp-loggingcpp17cpp20cross-platformfmtlibhigh-performancelog-libraryloggerlogginglogging-librarylow-latencymetricsobservabilityprometheusstructured-logging

Embed the badge

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

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

Questions

Does quill run?
Yes. quill runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test quill?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 6fcd9c01d303. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test quill?
The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does quill 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 quill need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing quill?
Nothing did, in the recorded run: zero errors between clone and running.
Where is the evidence for quill?
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.

Discussion