Parallelism != concurrency. Giving argument in forkjoinPool for parallelism doesnt limit the number of threads. This can grow exponentially if your task takes a lot if time.
Everyone knows Parallelism != Concurrency. When we create a ForkJoinPool using new ForkJoinPool(value), we are specifying the parallelism level (the number of threads that the pool will attempt to maintain). But, there's no guarantee that the number of threads will always match the specified value. The pool may dynamically adjust the number of threads to optimize performance and resource utilization. It might increase or decrease the number of threads based on workload and system conditions. So, while specifying a value provides a hint to the pool about the desired level of parallelism, it's not a strict constraint.
Your video was really nice not here to be rude. I wanted to share my experience recently, Previously: 200rps Threads: 200 Parallelism: 200 Now: 400rps Threads: 4000 Parallelism: 200 Again thankyou for the information and keep the work doing 🙌
