Making the word bigger doesn’t mean there’s more threads per, it just reduces the number of calls to complete some kinds of ops (and something about RAMing busses into each other and… cache locations? idk I’m sleepy)
The double deckers are an example of a ready-made solution in the original language’s standard library, the lower one is getting multithreading working through the C ABI bindings, using some 3rd party solution, all while multithreading a lot of other tasks in the application.
hang on, that first image is everything on a single thread…
Each bus is a timeslice
Nah, those are double deckers.
You sure they’re not dwords on a single bus?
Making the word bigger doesn’t mean there’s more threads per, it just reduces the number of calls to complete some kinds of ops (and something about RAMing busses into each other and… cache locations? idk I’m sleepy)
The double deckers are an example of a ready-made solution in the original language’s standard library, the lower one is getting multithreading working through the C ABI bindings, using some 3rd party solution, all while multithreading a lot of other tasks in the application.
Yeah, I can live with that. Well done!