You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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?
The text was updated successfully, but these errors were encountered: