onload VS threads

Other than that, I heard there's some 3rd party network libraries that are generally considered lower latency, one of them I believe either redhat uses for one of their systems, or it is sponsored by them: https://github.com/Xilinx-CNS/onload

I mean really you want to be doing some kind of (kernel network bypass with some sort of system programming language like C++ for low latency trading systems like this. Arb trading is usually not worth it unless you have a ton of expertise or some crazy mathematical edge that can offset. Plus you need to be guaranteed to execute the trade you ask for which most average joes don't have.

How about the x2 series from Xilinx?

It comes from solarflare who have a long pedigree of low-latency smartnics. They used to supply Cloudflare, and also supply like 50% of fintechs/financial markets.

You can also just use openonload to accelerate your programs. In this case just doing straight linux socket programming, which can be accelerated without dpdk. Or just use the generic linux driver if necessary.

https://github.com/Xilinx-CNS/onload

Ahki SingHania - Akhi is the engineering manager for the Execution team. He has a background in operating systems and networking. Before working on the Internet Computer, he worked on OpenOnload and Barrelfish.

https://github.com/Xilinx-CNS/onload any good?

It used to be openonload.org which seems to redirect to https://github.com/Xilinx-CNS/onload for the source to onload.

Similarly for threads: https://github.com/webassembly/threads

Specifically I submitted this to draw attention to the latest comment in the thread: https://github.com/WebAssembly/threads/issues/177

It's a good deep dive into how a small, but well-intentioned, browser choice nearly a decade ago led to poor outcomes for the WebAssembly ecosystem.

The answer is: it's complicated. Which is most of the time the answer in the WASI world.

For this case it's complicated because some runtime supports https://github.com/WebAssembly/threads which mostly contains things like the spec for atomic but not the actual "threads" specs and then some runtimes (i.e wasmtime) also supports https://github.com/WebAssembly/wasi-threads which is one version of the threads. But a new proposal came into play https://github.com/abrown/thread-spawn so ... it's complicated.

There’s a proposal for threads

WebAssembly is having/going to have threads

https://github.com/WebAssembly/threads

It's disappointing to see the WebAssembly/threads proposal is still only in proposal state, despite existing since 2018. It being just a proposal stops languages like golang from actually implementing support for it, despite Chrome supporting it since v70.

Ah, I should have clarified that I mean the assembly instructions for atomics, rather than the JavaScript API. I.e. the opcodes listed here: https://github.com/WebAssembly/threads/blob/master/proposals...

Another point to add here is that the current wasm specification does not support threads although there is a proposal to add one. So I imagine that till the wasm specification includes it, we will continue to have only single threaded canisters.