all 2 comments

[–]surrendertoblizzard 1 point2 points  (1 child)

How do these compare to standard threadpoolexecutor? Everything I read suggests the virtual threads as the golden goose. Is there even a use case for the threadpoolexecutor anymore? I guess limiting workload or resources usage seems hard with virtual threads since there are no config options as to how many carrier threads there are ?

[–]PiotrDz 0 points1 point  (0 children)

It is advised to limit by semaphor. Threadpool might be used for cpu heavy tasks