ual 0.7.4 preliminar benchmarks
Some early ual 0.7.4 benchmarking results across three backends: compiled with Go runtime, compiled with Rust runtime (rual), interpreted (iual).
No attempt has been made to make the new backends faster yet (iual, rual). That being said most concurrent code performs similarly across all three backends, and only interpreted ual (tree walker) sees an obvious penalty in compute heavy algorithms. I might --maaaybee-- be able to provide a VM for iual, but given the performance of the binaries using the Go and Rust backends it seems that it would be a better use of my time to keep adding important features that are still missing in this version. (file handling, sockets, for starters).
It seems to me that the ideal ual developer of the future will be happy to use iual for testing, and deliverable products will be compiled with one of the binary backend targets. The choice of Go or Rust will probably go down to environmental reasons, cultural aspects, or policy preference within organisations.
All in all, a highly productive day!
Now thinking of a fourth backend... wouldn't you guess what is it? 🙂


