News for hackers. Stuff that matters.
Re:JEP proposed to target JDK 19: 425: Virtual Threads (Prev... by SemanticStrengh on Monday May 02, 2022 @02:31PM (#31238954)
A major issue with loom is that it consume much more %CPU https://github.com/ebarlas/project-loom-comparison/blob/main... Edit no it is more efficient although it consume surprisingly high gpus at higher throughput than the others.
Re:JEP proposed to target JDK 19: 425: Virtual Threads (Prev... by didibus on Monday May 02, 2022 @02:48PM (#31239186)
Wouldn't that be expected when it also delivers more throughput and better latencies? It's handling more requests concurrently, so I'd expect the CPU usage to be higher, how else could it serve more requests faster otherwise?
Re:JEP proposed to target JDK 19: 425: Virtual Threads (Prev... by SemanticStrengh on Monday May 02, 2022 @02:57PM (#31239298)
Yes indeed I just find the consumption increase a but abrupt after 10K
Re:JEP proposed to target JDK 19: 425: Virtual Threads (Prev... by brokencode on Monday May 02, 2022 @02:41PM (#31239091)
Looking at the graphs, it uses less CPU for a given throughout, so it’s actually more efficient for CPU. It also provides lower latency and higher max throughout. It does seem to require more memory, though.
Re:JEP proposed to target JDK 19: 425: Virtual Threads (Prev... by pron on Monday May 02, 2022 @04:57PM (#31240838)
We expect to improve the memory consumption significantly in future releases. Some things had to be cut to make this release.
Re:JEP proposed to target JDK 19: 425: Virtual Threads (Prev... by SemanticStrengh on Monday May 02, 2022 @05:07PM (#31240937)
The existing data already looks excellent. I wonder if you could leverage SIMD/the vector api for speeding up some things. Or if value types will have an impact.