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
{{ message }}
This repository has been archived by the owner on Mar 9, 2022. It is now read-only.
Ideally, the sandbox container for windows should have different CPU shares with linux because:
windows sandbox container handles portforward;
windows cpu shares range is 5000-10000 (see here), which is different from 2-1024 on linux (see here).
However, we still use the same CPU shares for now, because:
The underlying job cpu rate control only supports 1-9 shares on windows, so it doesn't matter whether we use 2 or 20 here. (See here)
It is not clear how much cpu portforward will need. We may want to have a better default configured, or even make it configurable if it causes trouble for some users who rely on portforward heavily.
The text was updated successfully, but these errors were encountered:
Ideally, the sandbox container for windows should have different CPU shares with linux because:
However, we still use the same CPU shares for now, because:
The text was updated successfully, but these errors were encountered: