Repository navigation
Please put the ShadowsocksService into separate process for smaller memory footprint. #15
Description
Currently, ShadowsocksService shares the same process with the configuration UI. This leads to large amount of memory usage (15-20M), and is not optimal for long-running background service.
If separated into its own process (with "android:process" parameter in AndroidManifest.xml), the app process can be reclaimed soon after the configuration UI is closed, leaving ShadowsocksService only small amount of memory footprint (usually < 5M) for long-running.
Process separation does need more work on data passing-through, since no more shared memory space. I found the current implementation of ShadowsocksService was perfectly suitable for process separation, with all its configuration shared via SharedPreferences.
Activity
madeye commentedon May 26, 2013
Thanks for your advice. I have changed the logic as you said. If you'd like to have a try, just download the nightly build or build the latest code yourself.
oasisfeng commentedon May 26, 2013
Impressive response speed and nightly build! The ShadowsocksService now consumes only about 6M on my phone. :)