As far as I know, the zygote process starts the Java VM Runtime and
launches the first system_server Java process. system_server is the
core Android engine which starts the core Android services such as
ActivityManager, WindowManager, PackageManager, etc. Every other Java
process is started by zygote but is controlled by system_server.


On Dec 5, 12:34 pm, Ed <[EMAIL PROTECTED]> wrote:
> Wow, this is a tough one. I tried running top -n 1 from the adb shell
> after opening and closing a bunch of apps on my phone. Here's what it
> looks like so far:
>
> Prior to reboot:
>
>   PID CPU% S  #THR     VSS     RSS UID      Name
>    55  36% S    47 227780K  22252K system   system_server
>    36   3% S     3   3352K    444K compass  /system/bin/akmd
>  4241   3% R     1    904K    376K shell    top
>    87   0% S    15 114704K  14868K radio    com.android.phone
> .....
>   201   0% S     7  89964K   9708K app_33   edu.mit.locale
>  2251   0% S     8  91124K   9388K app_37
> com.fingerpainters.fingerpaint
>  2485   0% S     7 100372K  14312K system   com.android.settings
>  2497   0% S     6  87020K   9972K app_57
> com.streamfurious.android.free
>  2652   0% S     5  85884K   9828K app_43   com.tmobile.wifi
>  3496   0% S     8 103396K  17924K app_9    com.android.email
>  3575   0% S     7 106996K  13308K app_14   com.android.mms
>  3943   0% S     5  94296K  13916K app_89
> com.google.android.netmeter
>  4220   0% S     7  91816K  14632K app_6    com.android.calendar
>
> After reboot:
>
>   PID CPU% S  #THR     VSS     RSS UID      Name
>   234   4% R     1    904K    376K shell    top
>    17   0% S     1      0K      0K root     pdflush
>    18   0% S     1      0K      0K root     kswapd0
> .....
>    54   0% S    33 163312K  23608K system   system_server
>
> After launching and closing a bunch of apps:
>
>   PID CPU% S  #THR     VSS     RSS UID      Name
>    54   7% S    46 261352K  20256K system   system_server
>   871   4% R     1    904K    380K shell    top
>    38   3% S     3   3352K    560K compass  /system/bin/akmd
> .....
>   204   0% S     7  87948K  10384K app_43   com.tmobile.wifi
>   330   0% S     6  95436K  11804K app_76   com.punchometer
>   358   0% S     5  94764K  11604K app_66   com.mattwach.trap2
>   697   0% S     1    724K    312K shell    /system/bin/sh
>   760   0% S     5  94132K  11820K app_77   com.android.aKeyUI
>   765   0% S     5  85988K   9944K app_57
> com.streamfurious.android.free
>   771   0% S     5  96984K  15440K app_93   org.mmin.handycalc
>   780   0% S     5  97924K  14816K app_30   com.weather.Weather
>   814   0% S     5  94136K  12316K app_82
> com.johnlauricella.mymoney1
>   821   0% S     8 100928K  22404K app_9    com.android.email
>   830   0% S    12 104548K  14572K app_11   com.google.process.gapps
>   855   0% S     5  98260K  12400K app_49
> com.example.android.lunarlander
>   861   0% S     7  90088K  11144K app_37
> com.fingerpainters.fingerpaint
>
> My very uninformed conclusion: It does appear that "system_server" is
> providing some cleanup function and will continue to occupy a growing
> portion of the CPU utilization as one opens and closes applications. I
> don't know anything about it other than this. I did not see any app
> that stood out as a culprit--it seems they all add to system_server
> when you open and close them. I suspect that after a day or two of
> using apps, I will be back up above 30% CPU utilization for
> system_server.
>
> On Dec 5, 2:22 pm, Nickname <[EMAIL PROTECTED]> wrote:
>
> > From someones' observation pretty early around last spring, the
> > system_server MAY be collecting your garbage and loving the task.
>
> > Unless Android team has fixed the problem or identified that the
> > problem had never been there before releasing SDK 1.0,  sometimes
> > Android just appeared enamored of GC for hours even after DDMS showed
> > no more user app running....
>
> > Hope it's never there!!
>
> > On Dec 5, 9:26 am, Ed <[EMAIL PROTECTED]> wrote:
>
> > > I believe the bad apps are leaving something behind that are tying up
> > > the system. I will try running each app one at a time to see if I can
> > > get a better idea of the culprit(s).
>
> > > --Ed
>
> > > On Dec 5, 10:55 am, Mark Murphy <[EMAIL PROTECTED]> wrote:
>
> > > > Ed wrote:
> > > > > Thanks for your reply. Here's the result--the "system_server" is
> > > > > what's using the CPU right now:
>
> > > > >   PID CPU% S  #THR     VSS     RSS UID      Name
> > > > >    55  36% S    47 227780K  22252K system   system_server
> > > > >    36   3% S     3   3352K    444K compass  /system/bin/akmd
>
> > > > FWIW, I can tell you that system_server is as quiet as a church mouse on
> > > > my G1.
>
> > > > On the flip side, though, I have nary a clue what system_server
> > > > represents, other than given that it's running as "system", it's not an 
> > > > app.
>
> > > > --
> > > > Mark Murphy (a Commons Guy)http://commonsware.com
> > > > _The Busy Coder's Guide to Android Development_ Version 1.9 Available!
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Android Discuss" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/android-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to