CorePilot
How much faster is your machine with every core than with one?
Free right now — no account, no card
Preview
1 interface design, then a screenshot of it running. Drag, scroll or use the arrows.
Free while we’re in preview
Get CorePilot
How much faster is your machine with every core than with one?
The Mac button is for Apple Silicon. On an older Intel Mac, get this one instead.
One file, both ways. Double-click it for the window. Run the same file from a command prompt with arguments and it behaves as the command-line tool, because the engine is inside it. Nothing else to download and nothing to keep beside it.
Early preview. The window has been built and run, but not yet on a real Windows PC or Mac, so expect rough edges. The engine underneath it is fully tested.
- One file — no installer
- Runs on your machine, offline
- Source code published below
Free while in preview. It isn’t signed yet, so Windows or macOS will ask you to confirm the first time you open it. At launch, CorePilot is included in every plan along with the rest of the range.
One number, honestly derived
corepilot bench runs trial-division primality checking on a single goroutine for --duration (500ms by default), counts the checks completed, then runs the identical workload on runtime.NumCPU() goroutines for the same span. Each worker takes its own interleaved slice of the number range, so there’s no shared state, no locks and nothing to contend over.
You get ops/sec for each phase and the scaling factor between them. On this kind of embarrassingly parallel work, a healthy machine with light background load lands near its core count. CorePilot doesn’t editorialise about what counts as a good result, because virtualization, thermal behaviour and whatever else is running all move that number.
Wall clock is roughly twice --duration. --json if something downstream is parsing.
Read the memory line carefully
Sys, HeapAlloc and NumGC are the CorePilot process’s own Go runtime figures. Not system RAM. Not other processes.
Not in here
CPU or case temperatures, fan curves, affinity pinning, per-app profiles. All of those want vendor-specific hardware APIs that a portable Go binary can’t reach. If you want disk throughput instead, that’s DiskOps.
Reading on the job itself
- Is my computer actually getting slower? Time the same thing thirty times and keep the median, not the average. One slow run is noise; a median that...
Advanced & technical details Command-line builds, source code, checksums and a recorded session — for developers and IT teams
A working CLI prototype of the benchmark half of the job: a live single-thread vs. multi-thread CPU benchmark with a real scaling factor, plus this process's own Go-runtime memory stats. Real temperatures, fan curves, CPU affinity control, and per-app performance profiles need OS-privileged hardware APIs and are on the roadmap.
Naming status
Working name only — brand verdict **AVOID** (Very High). Collision: CorePilot. Rename completely.
What it draws on
Existing paid software whose best ideas shaped this program: Process Lasso Pro, AIDA64 Extreme, HWiNFO Pro, Argus Monitor.
Command line
There is nothing extra to install. The program you download is the command-line tool as well: give it arguments instead of double-clicking it and it runs as one, with its output on your terminal. The standalone builds below are the same engine on its own, for machines where you would rather not ship a window at all.
CorePilot - performance console prototype (CPU benchmark + runtime memory stats)
Usage:
corepilot bench [--duration 500ms] [--json]
Commands:
bench Run a live single-thread vs. multi-thread CPU benchmark and
report Go runtime memory stats.
Flags for "bench":
--duration duration How long to run each phase (single-thread, then
multi-thread) for. Accepts Go duration syntax,
e.g. 500ms, 2s, 1m. (default 500ms)
--json Emit structured JSON instead of a text report.
-h, --help Show this help.
Notes:
- Total wall-clock time is roughly 2x --duration, since the single-thread
and multi-thread phases run one after another, not concurrently.
- Memory stats reported are for the CorePilot process's own Go runtime,
NOT total system RAM or other processes' usage.
- Temperatures, fan curves, CPU affinity control, and per-app performance
profiles are on the roadmap; see ../plan.md. They need OS-privileged,
vendor-specific hardware APIs not available to a portable, dependency-
free Go CLI.Recorded from the shipped binary, not written by hand.
Source
Every file the program is built from:
console.go · console_test.go · guided.go · main.go
SHA-256 checksums · build instructions & scope notes · full build plan