Num threads in Java streams on Kubernetes

How many threads are spawned by Java Parallel Streams when deployed in Kubernetes with 0.8 milliCPU?

Java Parallel Streams spawn a number of threads based on the number of cores the machine has available. When a service is deployed in Kubernetes with a 0.8 milliCPU limit, it is expected that the number of threads spawned by the parallel streams (ForkJoinPool) will range from 0-1.

Is there any additional information that influences the number of threads spawned in this environment?

Any insights into the dynamic behavior of the threads in this type of environment would be greatly appreciated.

In the given environment of Kubernetes with a 0.8 milliCPU limit, the number of threads spawned by Java Parallel Streams (ForkJoinPool) will range from 0-1. The additional information that can influence the number of threads spawned includes the number of available cores in the machine and the workload of the application. The dynamic behavior of the threads in this environment depends on factors like the number of tasks, the complexity of the tasks, and the availability of CPU resources.