[kristjansson]

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

[jloveless]

https://github.com/l-labs/master-benchmark

[jazza68]

that 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]

I think one day we'll do that on https://oxide.computer/ 1: because we love our friends 2: the gear is great (and ROCEv2 supported which L uses)

[kristjansson]

ah. cheeky.

[kristjansson]

Seems 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]

I’d encourage running the master bench yourself! Super easy

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