AltSql Ask ยท Live demo
Ask 500 machines one question
Each machine keeps a day of readings in its own AltSql database. You ask in SQL. The gateway turns the question into a small program, every machine answers from its own records, and only the answers travel back.
Simulated machines, real engines. The machines, their readings and the network are simulated. AltSql Core and AltSql Ask run in this page, compiled to WebAssembly.
The fleet
Loading the engine
Ask the fleet
Pick a question or write your own. Every machine has the table raw (time, temp, vib), with a reading every two minutes for a day (time in seconds from midnight), and the table kv (key, value) of its settings. It can also be asked about its device, plant and fw (firmware) as if they were columns.
What each machine receives
The program, byte by byte
The same program, readable
One machine's answer
The answer
Bytes on the network
What this question cost, against pulling every machine's data to the gateway first. Every figure is counted in this page, byte by byte.
Check the answer
The gateway pulls all 360,000 readings into one database and runs the same SQL there with AltSql Core. The two answers should be the same.
Try to break it
A question from the gateway must never hang a machine, fill its memory or change its data. Each program carries limits, and each machine checks the program before it runs a single step.
What is real here
Real
- AltSql Ask: the compiler on the gateway, the runner on every machine, and the merge.
- AltSql Core: each machine's database, and the reference database for the check.
- Every byte of every program and answer, and every step counted against the budget.
Simulated
- The 500 machines and their readings, from a fixed script, so the numbers are the same every time.
- The network: delays, and the weak links that answer late.
- The flash chips, emulated in memory the way the engine sees real NOR flash.