Quote:
Originally Posted by milesnapue
All marginal I believe because of how processes are handled. not running processes won't harm anything but if you kill processes that want to be running they will start up again. Try doing five tests in a row before and after killing to get a good average?
|
I have done what you suggested... I went to a higher clock speed of 825Mhz and got results that confirm your speculation.
There are very minor differences between a bunch of apps running and after killing them. CPU is all that showed a large change.
Quote:
Originally Posted by Ludacrisvp
I have running the TP2 @ 700Mhz
Class 4 - 4Gb SD
WM 6.5.5 - energyROM
Android latest kernel pkg as of 3-23
Before killing my running applications
Graphic Total - 8.620707
CPU Total - 157.22702
Memory Total - 134.70012
Filesystem Total - 38.16194
BenchmarkPI app
Calculated PI in 10310ms
After killing running applications
Graphic Total - 9.040954
CPU Total - 212.3994
Memory Total - 149.32158
Filesystem Total - 32.666462
BenchmarkPI app
Calculated PI in 10260ms
|
I have running the TP2 @
825Mhz
Class 4 - 4Gb SD
WM 6.5.5 - energyROM
Android latest kernel pkg as of 3-30
Before killing my running applications 5x avg scores
Graphic Total - 10.393171
CPU Total - 235.04466
Memory Total - 148.54222
Filesystem Total - 36.460995
BenchmarkPI app
Calculated PI in 8560ms
After killing running applications 5x avg scores
Graphic Total - 10.364183
CPU Total - 242.02277
Memory Total - 157.17532
Filesystem Total - 34.137127
BenchmarkPI app
Calculated PI in 8460ms