tile38
Real-time Geospatial and Geofencing
Runssource: GitHubhomepageGoMITcommit a9f953e358d3
Go, MIT licensed. The project labels itself: database, geo, geofences, geospatial, index, location and spatial.
tile38 runs. An Argusic agent installed it in 5 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
tile38-server, tile38-cli, and tile38-benchmark compiled from source; server starts, answers HTTP on localhost, and passes the full integration test suite (98/98 subtests) plus all internal package tests with 0 failures.
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
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.
- git describe --tags failed: no tags found in repo1 minute
- Install time
- 5 minutes
- Cold machine to finish
- 15 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- go test -v ./tests/ passed (1 integration test, 98 subtests); live tile38-server on port 19852 answered SET/GET/NEARBY over HTTP with correct JSON responses
- Model tokens used
- 73,309
- Exact commit tested
- a9f953e358d3
- 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.
PASS ok github.com/tidwall/tile38/tests 13.102s Everything is working end to end. Let me produce the final result. **Error encountered and fixed:** `make` failed initially because `git describe --tags --abbrev=0` r… **All tests pass.** Full suite: 1 integration test with 98 subtests across keys, JSON, search, CLI,… **Live server verified:** launched `tile38-server` on port 19852, issued SET/GET/NEARBY commands ov… tokens used 73,309 Everything is working end to end. Let me produce the final result. **Error encountered and fixed:** `make` failed initially because `git describe --tags --abbrev=0` r… **All tests pass.** Full suite: 1 integration test with 98 subtests across keys, JSON, search, CLI,… **Live server verified:** launched `tile38-server` on port 19852, issued SET/GET/NEARBY commands ov…
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.
- Recovered from all 1 error 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.
What did not, or is not known
- Took 5 minutes to install, slower than the median of the 26 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 27 database projects Argusic has installed and timed, tile38 was the 18th fastest to reach a running state, and 22 of 27 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 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)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/tile38)Questions
- Does tile38 run?
- Yes. tile38 runs. Argusic installed and launched it on a clean machine in 5 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test tile38?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit a9f953e358d3. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test tile38?
- The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does tile38 take to install?
- 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 tile38 need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing tile38?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does tile38 compare with the alternatives?
- Of the 27 database projects Argusic has installed and timed, tile38 was the 18th fastest to reach a running state, and 22 of 27 reached one at all.
- Where is the evidence for tile38?
- 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.