4 ms·
This is a very cool idea, and I wonder if eventually we'll see new tooling spring up to support this. Running coroutines like this seems like it would potentia
by brian-armstrong 8y ago
This is a very cool idea, and I wonder if eventually we'll see new tooling spring up to support this.
Running coroutines like this seems like it would potentially create more cache pressure. Is the idea that you'll execute instructions you already have loaded, so you won't incur any cache misses for instructions?
- yxhuvud 8y agoIt is more about memory pressure than instruction pressure - the idea is that when an algorithm finds itself having to fetch something from memory, it can issue a prefetch, then take a step back and handle other requests while waiting for the result. How this would fare in a real world scenario that isn't a benchmark but in a system that is also doing other stuff at the same time is anyones guess though.
- tuukkah 8y agoTheir benchmark is close to what a relational database does in the real world. They also cite previous work "Interleaving with Coroutines: A Practical Approach for Robust Index Joins", which implements this succesfully in the SAP HANA column store. I don't think it matters what else the system is doing as long as a complete core is available for running this.