3 ms·
I tried explaining that here: https://inside.java/2020/08/07/loom-performance/ https://inside.java/2020/08/07/loom-performance/
by pron 6y ago
I tried explaining that here: https://inside.java/2020/08/07/loom-performance/ https://inside.java/2020/08/07/loom-performance/
- x87678r 6y agoThanks I'm honored you're replying. :) Looks like performance improvement will be nice.
- Traubenfuchs 6y agoDo you know if Loom has any implications for reactive frameworks, like reactive spring? Or do they already contain a... "non native" implementation of this concept? https://spring.io/reactive https://spring.io/reactive
- pron 6y agoWith Loom, the simple, blocking, non-reactive frameworks (like Spring MVC) should give you similar throughput to the reactive ones -- that's the main impact. I don't know how reactive frameworks intend to make use of Loom.
- The_rationalist 6y agoLoom will be a performance game changer even for reactive frameworks. I'm not even talking about it the fact it use io_uring and other SOTA OS technologies. I'm talking about the fact it allows to have a non blocking socket thus enabling for the first time asynchronous jdbc access and thus postrgresql pipelineing/batching. This will allow spring to come at the top 4 fastest http servers on earth according to the benchmarckgame