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
I'm running SS + v2ray plugin on a Centos 7 x64 min setup 128Mb RAM. Clean SS with no plugins bring my system memory to 60Mb usage after reboot. Enabling v2ray as a plugin brings it to 100-105Mb. If I connect with client and start to use proxy setup it eventually reaches OoM, easiest way to repro is via speedtest.net
Is this normal/expected behavior? How high are the requirements? As far as I know GO uses GC so I assume it allocates too much in a short period of time without a chance to collect. Is there any option to setup GC more aggressively for collection?
The text was updated successfully, but these errors were encountered:
I'm running SS + v2ray plugin on a Centos 7 x64 min setup 128Mb RAM. Clean SS with no plugins bring my system memory to 60Mb usage after reboot. Enabling v2ray as a plugin brings it to 100-105Mb. If I connect with client and start to use proxy setup it eventually reaches OoM, easiest way to repro is via speedtest.net
Is this normal/expected behavior? How high are the requirements? As far as I know GO uses GC so I assume it allocates too much in a short period of time without a chance to collect. Is there any option to setup GC more aggressively for collection?
The text was updated successfully, but these errors were encountered: