project-loom-c5m
remove-recursion-insp
project-loom-c5m | remove-recursion-insp | |
---|---|---|
16 | 1 | |
350 | - | |
- | - | |
0.0 | - | |
about 2 years ago | - | |
Java | ||
MIT License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
project-loom-c5m
-
Java 21: The Nice, the Meh, and the Momentous
It is not. Blocking IO (with some exceptions mentioned in the JEP) will automatically be translated by the runtime into non-blocking IO when it occurs on virtual threads, and no OS threads will be blocked. You can have a million threads blocking on a million sockets (obviously without creating a million OS threads): https://github.com/ebarlas/project-loom-c5m
You can't do that with thread pools. You could achieve that scalability with async code, but then observability tools will not be able to track the IO operations and who initiated them, but with virtual threads you'll see exactly what business operation is doing what IO and why.
-
Don’t call it a comeback: Why Java is still champ
That might change in JDK 21 (with virtual threads). See this https://github.com/ebarlas/project-loom-c5m . It achieve 5 million persistent connections (again depends on the server capacity and kernal tuning) using normal simple blocking code (https://github.com/ebarlas/project-loom-c5m/blob/main/src/main/java/loomtest/EchoServer.java) . It's a far better better programming model compared to JS async/await.
- Project loom + valhalla + graalvm = Java on steroids
- Distilling the Real Cost of Production Garbage Collectors
- Achieving 5M persistent connections with Project Loom virtual threads
- Experiment to achieve 5M persistent connections with Project Loom (Java)
- What is the current state of the art for efficiently handling blocking requests in Java/Spring?
remove-recursion-insp
-
Experiment to achieve 5M persistent connections with Project Loom (Java)
Thanks for posting that link to Java tail recursion library, super handy + didn't know about it. You need tail recursion for writing expression evaluators/visitors frequently.
I've been using an IntelliJ extension that can do magic by rewriting recursive functions to stateful stack-based code for performance, but it spits out very ugly code:
https://github.com/andreisilviudragnea/remove-recursion-insp...
What are some alternatives?
jvm-tail-recursion - Optimizer library for tail recursive calls in Java bytecode
remove-recursion-inspection - Intellij IDEA inspection for automatic recursion detection and removal
project-loom-comparison - A comparison of different methods for achieving scalable concurrency in Java
Reactive Streams - Reactive Streams Specification for the JVM
qbicc - Experimental static compiler for Java programs.
Jooby - The modular web framework for Java and Kotlin
pidove
junit5-looming - 🧵 JUnit 5 Test Engine using Virtual Threads
ktor - Framework for quickly creating connected applications in Kotlin with minimal effort