If I understand correctly, the calculator by default assumes 250M for the threads. When using virtual threads, this is probably a quite exaggerated number. Would it be possible to detect (or explicitly spell out) that the Java application is using virtual threads, and as a result lower the amount of required memory for them?
If I understand correctly, the calculator by default assumes 250M for the threads. When using virtual threads, this is probably a quite exaggerated number. Would it be possible to detect (or explicitly spell out) that the Java application is using virtual threads, and as a result lower the amount of required memory for them?