gel

Gel supercharges Postgres with a modern data model, graph queries, Auth & AI solutions, and much more.

Runs with mockssource: GitHubhomepagePythonApache-2.0commit 85191063b4db

Python, Apache-2.0 licensed. The project labels itself: database, edgedb, edgeql, gel, graph relational, high performance and relational database.

gel runs, with stand-ins for the services it depends on. An Argusic agent installed it in 18 minutes and hit 9 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Gel server is installed with all 18 Cython extensions and 3 Rust PyO3 extensions built; the EdgeQL parser, schema parser, tracer, and interpreter disambiguation test suites pass (901 tests total); the server CLI reports version 8.0-dev; database-backed tests require a PostgreSQL backend not present in this container.

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

At a glance

verdict
Runs with mocks
Argusic Score
86 / 100
cost of the verifying run
$0.37 (measured)
recorded runs
2
last tested
stars
14,188
forks
452
open issues
947
watchers
99
size
74 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 gel, 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.

  • postgres configure fails5 minutes
  • missing python3.12-dev headers3 minutes
  • missing protobuf-c.h2 minutes
  • missing _buildmeta.py2 minutes
  • Rust compiler not found1 minute
  • no git tags for version detection1 minute
Install time
18 minutes
Cold machine to finish
82 minutes
Errors hit and fixed
9 hit, 9 fixed with no human help
How the result was proved
python3 -m unittest tests.test_edgeql_syntax passed (719 tests, OK), tests.test_schema_syntax passed (171 tests, OK), tests.test_tracer passed (5 tests, OK), tests.test_interpreter_disambiguation passed (6 tests, OK). All 3 Rust extensions and all 18 Cython extensions import successfully. gel-server binary responds to --help.
Model tokens used
1,714,520
Exact commit tested
85191063b4db
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
Behaviour against real services
this run was verified against stand-in services only

The end of the recording

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

| Rust/Cargo not found | Cargo was not installed | Installed via `rustup` | 1 min |
| `max() iterable argument is empty` | No git tags for version detection | Created `v8.0.0b1` tag |…
| `Python.h: No such file or directory` | Missing `python3.12-dev` headers | Downloaded `libpython3…
| `protobuf-c/protobuf-c.h: No such file or directory` | Missing `libprotobuf-c-dev` | Downloaded .…
| Submodules empty | `git submodule init` needed | Ran `git submodule update --init --recursive` | …
| Postgres `configure` fails | Build tries to compile Postgres | Used `BUILD_EXT_MODE=skip` for pip…
| `can't find Rust compiler` | PATH didn't include `$HOME/.cargo/bin` | Exported PATH before runnin…
| `could not find VERSION/SHARED_DATA_DIR in build metadata` | Missing `_buildmeta.py` | Created cu…
| `pg_config output did not provide BINDIR value` | No PostgreSQL installed | Created mock `pg_conf…
```
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 18, "errors": [{"msg": "Ru…
```

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

  • Recovered from all 9 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed Apache-2.0, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
  • Took 18 minutes to install, slower than the median of the 36 comparable projects Argusic has measured.

Of the 37 database projects Argusic has installed and timed, gel was the 34th fastest to reach a running state, and 31 of 37 reached one at all.

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 mocks92.000.37
Argusic Runner1/3Unverified80.000.18

Topics (from GitHub)

databaseedgedbedgeqlgelgraph-relationalhigh-performancerelational-database

Embed the badge

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

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

Questions

Does gel run?
gel runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 18 minutes, hitting 9 errors on the way, and recorded the session.
How did Argusic test gel?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 85191063b4db. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test gel?
The run that produced this verdict cost $0.37: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does gel take to install?
18 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 gel need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing gel?
9 things broke in the recorded run, and 9 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does gel compare with the alternatives?
Of the 37 database projects Argusic has installed and timed, gel was the 34th fastest to reach a running state, and 31 of 37 reached one at all.
Where is the evidence for gel?
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