3 ms·
Quite cool, but for a new runtime of an existing language it might make sense to compare to, y'know, the other[0] runtimes of that language? Even if one has to
by kristjansson 4mo ago
Quite cool, but for a new runtime of an existing language it might make sense to compare to, y'know, the other[0] runtimes of that language? Even if one has to omit the best, closed ones for lack of access / permission to benchmark?
[0]: https://k.miraheze.org/wiki/Running_K https://k.miraheze.org/wiki/Running_K
- jloveless 4mo agohttps://github.com/l-labs/master-benchmark https://github.com/l-labs/master-benchmark
- kristjansson 4mo agoah. cheeky.
- kristjansson 4mo agoSeems like the only point of comparison against a competitive k/q runtime is an MBP run? suggestive to be sure, but would be good to see some other machines, esp. an x86. Seems wild that the much-lauded "reference engine" leaves ~2x perf improvements on the table.
- jloveless 4mo agoI’d encourage running the master bench yourself! Super easy https://github.com/l-labs/master-benchmark https://github.com/l-labs/master-benchmark Or on the database side of the house try the h2o.ai base that duckdb excels at https://github.com/l-labs/db-benchmark/tree/main/l https://github.com/l-labs/db-benchmark/tree/main/l
- jazza68 4mo agothat is fast! Are you going to do the STAC-M3 benchmarks? Kx use them as evidence that they are the fastest, which is a fair claim as nobody else participates in that particular test :-)
- jloveless 4mo agoI think one day we'll do that on https://oxide.computer/ https://oxide.computer/ 1: because we love our friends 2: the gear is great (and ROCEv2 supported which L uses)