I suspect that compcache is not interacting properly with android but I need some stats to really analyze it. This should be standardized so please answer as I request and avoid any "me too" type answers.
Here's what you need:
Compcache running or a linux swap partition or file (swapper counts).
The default browser bound to a shortcut (search-b) and set to load www.cnn.com as your homepage. Close extra windows before starting and go there at least once. Make sure you're blocking popups.
A homescreen where you have icons and widgets that you have noticed in the past have taken time to load.
Music player to run in the background if you need to increase the system load.
Optionally: Gmail bound to a keyboard shortcut. (search-g for me)
Adb shell and knowledge to run these tests.
Here's what you're doing:
adb shell into your phone
Grab following stats (you can copy and paste in on one line):
Code:
uname -r;uptime;cat /proc/sys/vm/swappiness;cat /proc/swaps;cat /proc/ramzswap;free
Hit home button and go to homescreen. Take note of whether the homescreen needed to reload everything or if it was snappy. After completely done loading, run 'free' and record.
Keyboard shortcut to browser. Take note of whether the browser had to download and reload everything. After completely done loading, run 'free' and record.
Repeat 3-4 until either:
switching is always snappy,
the value of 'free' for swap ceases to change significantly while apps are reloading (like +-100 over 2-3 slow reloads),
or the value of 'free' for swap maxes out (note if you start getting lots of force closes).
Code:
total used free shared buffers
Mem: 97876 95492 2384 0 644
Swap: 43880 [B] 404[/B] 43476
Total: 141756 95896 45860
If its always snappy, put more load on the system by setting the music player in the background. If that still doesn't stress the system, throw in Gmail in the mix randomly. Note if snappy, and record 'free' stats.
If you're using both compcache and a linux swap, try to get information at the point where you've crossed over from compcache to linux swap. So if you're compcache is only 8 megs, seeing the difference as your swap fills over the 8 meg boundary is useful.
Finally, here's what you should report, either by putting it into a text file and attaching, or by placing it into a
Code:
block.
[list=1][*]Mod used. e.g. Cyanogen 3.9
[*]Info from step 2) above. [code]2.6.29-cm
12:47:45 up 3:43, load average: 2.13, 2.05, 2.09
15
Filename Type Size Used Priority
/dev/ramzswap0 partition 12284 408 -1
/system/sd/swapfile.swp file 31596 0 -2
DiskSize: 12288 kB
NumReads: 33
NumWrites: 102
FailedReads: 0
FailedWrites: 0
InvalidIO: 0
PagesDiscard: 0
ZeroPages: 3
GoodCompress: 77 %
NoCompress: 9 %
PagesStored: 99
PagesUsed: 31
OrigDataSize: 396 kB
ComprDataSize: 118 kB
MemUsedTotal: 124 kB
total used free shared buffers
Mem: 97876 95720 2156 0 632
Swap: 43880 408 43472
Total: 141756 96128 45628
[*]Results from repeating 3-4. If it ended up being too responsive and you couldn't stress it just include one cycle. Mark what you swapped to and whether it reloaded (Y for yes). e.g.
Code:
home
total used free shared buffers
Mem: 97876 95824 2052 0 292
Swap: 24464 2268 22196
Total: 122340 98092 24248
browser Y
total used free shared buffers
Mem: 97876 96032 1844 0 252
Swap: 24464 2540 21924
Total: 122340 98572 23768
home
total used free shared buffers
Mem: 97876 94436 3440 0 264
Swap: 24464 2940 21524
Total: 122340 97376 24964
browser Y
total used free shared buffers
Mem: 97876 95960 1916 0 280
Swap: 24464 5292 19172
Total: 122340 101252 21088
home Y
total used free shared buffers
Mem: 97876 92868 5008 0 272
Swap: 24464 6484 17980
Total: 122340 99352 22988
[/list]
Thanks!
Reserved for my test results.
Another good test is iMeem. This app is a memory whore and really puts pressure on the system.
Code:
Cyanogen 3.6.8.1
2.6.29-cm
15:19:09 up 5:28, load average: 7.58, 5.31, 4.33
20
Filename Type Size Used Priority
/dev/ramzswap0 partition 24464 15968 -1
DiskSize: 24468 kB
NumReads: 7817
NumWrites: 8908
FailedReads: 0
FailedWrites: 0
InvalidIO: 0
PagesDiscard: 0
ZeroPages: 241
GoodCompress: 65 %
NoCompress: 12 %
PagesStored: 5871
PagesUsed: 2370
OrigDataSize: 23484 kB
ComprDataSize: 9323 kB
MemUsedTotal: 9480 kB
total used free shared buffers
Mem: 97876 95852 2024 0 560
Swap: 24464 15968 8496
Total: 122340 111820 10520
home Y
total used free shared buffers
Mem: 97876 96348 1528 0 776
Swap: 24464 14600 9864
Total: 122340 110948 11392
browser Y
total used free shared buffers
Mem: 97876 96528 1348 0 420
Swap: 24464 14844 9620
Total: 122340 111372 10968
home Y
total used free shared buffers
Mem: 97876 96432 1444 0 752
Swap: 24464 14792 9672
Total: 122340 111224 11116
browser Y
total used free shared buffers
Mem: 97876 96484 1392 0 404
Swap: 24464 14844 9620
Total: 122340 111328 11012
home Y
total used free shared buffers
Mem: 97876 96464 1412 0 668
Swap: 24464 15048 9416
Total: 122340 111512 10828
No other posts? C'mon everyone, these statistics will help YOU get a faster, better configured phone.
**********
sha.goyjo said:
I'm going to be the first to say it. Doing tests on compcache .5 is somewhat pointless atm. If you follow Cyanogens, you'll see that he's currently working with the compcache people on an arm revision of .6, which uses a VERY different code base. I'd contribute to your thread if it wasn't trying to fiddle with a version that was just an arm patch on the existing compcache branch. You'd be better off waiting till the .6 goes stable on the trunk. All that being said, if you want to try and rewrite kernel modules that are in the process of being re-re-written, be my guest.
Not trying to be an ass, just trying to save us all some time by working towards things efficiently.
That being said, .6 could REALLY use some people working on it. Once it gets working we'll be able to use backing swap files instead of a partition, which would be great. No more Linux-swap on an sdcard.
Click to expand...
Click to collapse
Hmm. So what you are saying is that we should find no significance in the fact the cyanogen already posted in this thread with supportive info for the tests.
Also, in regards to your work on .6, what benchmarking plan did you have to prove:
1) that .6 performs better than .5 on our phones
2) that .6 performs better than a linux swap on our phones
3) that .6 performs better than .5 with a backing swap on our phones
Please note that any answers to this thread could help build these benchmarks for you.
Running CM 3.8
Browser only reloaded once...even with music playing, and running wisepilot! Even the one reload was a quick one.
Code:
2.6.29-cm
18:05:17 up 1:13, load average: 2.75, 3.69, 4.14
60
Filename Type Size Used Priorit
/dev/ramzswap0 partition 31996 21264 -1
DiskSize: 32000 kB
NumReads: 15024
NumWrites: 16558
FailedReads: 0
FailedWrites: 0
InvalidIO: 0
PagesDiscard: 246
ZeroPages: 196
GoodCompress: 75 %
NoCompress: 4 %
PagesStored: 7804
PagesUsed: 2977
OrigDataSize: 31216 kB
ComprDataSize: 11516 kB
MemUsedTotal: 11908 kB
total used free shared buffers
Mem: 97876 96376 1500 0 576
Swap: 31996 21264 10732
Total: 129872 117640 12232
#
From CNN to Home
**snappy
total used free shared buffers
Mem: 97876 95752 2124 0 588
Swap: 31996 22040 9956
Total: 129872 117792 12080
From Home to CNN
**snappy no reload
total used free shared buffers
Mem: 97876 96032 1844 0 520
Swap: 31996 22020 9976
Total: 129872 118052 11820
#
ADDED MUSIC PLAYER BACKGROUND And checked mem
total used free shared buffers
Mem: 97876 95964 1912 0 624
Swap: 31996 17516 14480
Total: 129872 113480 16392
FROM HOME TO CNN
**Reload
total used free shared buffers
Mem: 97876 96120 1756 0 448
Swap: 31996 24780 7216
Total: 129872 120900 8972
CNN to Home
**Snappy...no redraw
total used free shared buffers
Mem: 97876 96400 1476 0 492
Swap: 31996 29248 2748
Total: 129872 125648 4224
Home to Browser
***Snappy NO RELOAD WITH MUSIC RUNNING!!!
total used free shared buffers
Mem: 97876 96288 1588 0 464
Swap: 31996 26660 5336
Total: 129872 122948 6924
ADDED WISEPILOT NAVIGATION mUSIC STILL RUNNING
total used free shared buffers
Mem: 97876 96532 1344 0 396
Swap: 31996 27592 4404
Total: 129872 124124 5748
WISEPILOT RUNNING, MUSIC RUNNING, SWITCHED TO CNN from within wisepilot (search b)
***NO RELOAD, NO LAG....
total used free shared buffers
Mem: 97876 95988 1888 0 492
Swap: 31996 27208 4788
Total: 129872 123196 6676
#
double posted
by the way, in case everyone missed it:
I have two G1's. Both have brand new installs of CM 3.9. One has compcache (with swapiness set to 20 and 24mb of space allocated) and one does not. After a reboot on both devices and waiting a five minutes for everything to settle, I filmed the opening of the camera app. The one without compcache is noticeably quicker. Is compcache slowing our machines down, at least in certain instances?
By the way, cat /proc/ramzswap confirms compcache is enabled.
http://www.youtube.com/watch?v=gNYv-5WLDVA
edit:swappiness for the above tests was at 60....
Running Cyanogen 3.8.1 with the Palm Pre theme ( dunno if it made a diff.) and HTC Music app running.
Code:
2.6.29-cm
03:53:53 up 3 min, load average: 2.22, 1.47, 0.60
60
Filename Type Size Used Priority
/dev/ramzswap0 partition 31996 11612 -1
DiskSize: 32000 kB
NumReads: 1902
NumWrites: 3415
FailedReads: 0
FailedWrites: 0
InvalidIO: 0
PagesDiscard: 0
ZeroPages: 137
GoodCompress: 72 %
NoCompress: 4 %
PagesStored: 3278
PagesUsed: 1128
OrigDataSize: 13112 kB
ComprDataSize: 4461 kB
MemUsedTotal: 4512 kB
total used free shared buffers
Mem: 97876 96488 1388 0 652
Swap: 31996 11612 20384
Total: 129872 108100 21772
Home Y
total used free shared buffers
Mem: 97876 95704 2172 0 668
Swap: 31996 11612 20384
Total: 129872 107316 22556
Browser Y
total used free shared buffers
Mem: 97876 96308 1568 0 432
Swap: 31996 15528 16468
Total: 129872 111836 18036
Home N
total used free shared buffers
Mem: 97876 86336 11540 0 468
Swap: 31996 14936 17060
Total: 129872 101272 28600
Browser Y
total used free shared buffers
Mem: 97876 95196 2680 0 520
Swap: 31996 14932 17064
Total: 129872 110128 19744
Home N
total used free shared buffers
Mem: 97876 96176 1700 0 460
Swap: 31996 15056 16940
Total: 129872 111232 18640
Browser (Opened up really quick) N
total used free shared buffers
Mem: 97876 96432 1444 0 540
Swap: 31996 15200 16796
Total: 129872 111632 18240
Home N
total used free shared buffers
Mem: 97876 96096 1780 0 540
Swap: 31996 15208 16788
Total: 129872 111304 18568
pinetreehater said:
by the way, in case everyone missed it:
I have two G1's. Both have brand new installs of CM 3.9. One has compcache (with swapiness set to 20 and 24mb of space allocated) and one does not. After a reboot on both devices and waiting a five minutes for everything to settle, I filmed the opening of the camera app. The one without compcache is noticeably quicker. Is compcache slowing our machines down, at least in certain instances?
By the way, cat /proc/ramzswap confirms compcache is enabled.
http://www.youtube.com/watch?v=gNYv-5WLDVA
edit:swappiness for the above tests was at 60....
Click to expand...
Click to collapse
I'm not surprised it was.
Without compcache : Start camera app, realize your out of memory, kill another application (meaning it will start slower the next time, going through full initialization).
With compcache : Start camera, push inactive application into compcache.
I'd like to see some similar tests with more tests run. I think I might actually write a little app for this.
derfolo said:
Hmm. So what you are saying is that we should find no significance in the fact the cyanogen already posted in this thread with supportive info for the tests.
Also, in regards to your work on .6, what benchmarking plan did you have to prove:
1) that .6 performs better than .5 on our phones
2) that .6 performs better than a linux swap on our phones
3) that .6 performs better than .5 with a backing swap on our phones
Please note that any answers to this thread could help build these benchmarks for you.
Click to expand...
Click to collapse
No, I apologize for being offensive. Part of my reasoning has more to do with the fact that, as far as I have seen, regardless of what works best people tend to move to the latest version. It wasn't a utility prediction. In that respect, you are going in the right direction. I do think that the plans to implement dynamic swapping between backing and ramz in the future really make a big difference, however, in any kind of work we are trying to do here. Also, from what I've looked at the difference in the modules, they look significantly different now.
I didn't mean to press your buttons, but what I'm saying does have merit.
I say this because it's not about benchmarking the current version vs. the new version. That kind of a benchmark doesn't work, because the new version has an improved feature set. Software with a larger feature set rarely performs better than software with a smaller feature set. However, the features inherent in compcache .6 are VERY compelling for android phones, specifically the ability to use backing_swap from a FILE instead of a partition. The fewer partitions on your sdcard, the better. Less wasted space, and less time spend confusing the kernel as to which /dev/ it should be writing to at the time.
As to cyanogen having "supported" your tests, there are a lot of good reasons for it. You could discover a kernel interfacing problem. You could discover a problem in the arm patch that would be relevant to the new version or upgraded versions of CM.
All I think is that the compcache project could use all the help it can get rolling out .6 for android, and that if more people helped them with that, maybe we could try and find ways to fix the version of compcache we'll be using, instead of the one we'll be moving away from.
One thing people need to realize is that there is no free lunch. Swap (whether the partition or compcache) is not for speeding up the system but for allowing you to run many big apps together at the same time.
swap will slow you down a bit, whether its compcache (cpu overhead for compression) or partition (I/O overhead). So, stop fooling yourself. If you want a fast phone, just use basic things and leave swap out of picture. if you want a fast phone AND want to run tonnes of stuff like touchflo, get a phone with more RAM.
test results
devsk said:
One thing people need to realize is that there is no free lunch. Swap (whether the partition or compcache) is not for speeding up the system but for allowing you to run many big apps together at the same time.
swap will slow you down a bit, whether its compcache (cpu overhead for compression) or partition (I/O overhead). So, stop fooling yourself. If you want a fast phone, just use basic things and leave swap out of picture. if you want a fast phone AND want to run tonnes of stuff like touchflo, get a phone with more RAM.
Click to expand...
Click to collapse
Correct me if I'm wrong, but it sounds rather like you're saying, "Stop trying to make things better." Rather an odd sentiment for a Development forum, no?
I ran this test with just Calendar and Weather widgets running on the home screen and, although I have occasionally found the entire home screen slow to reload during regular use, during this test the home screen never seemed to reload at all, even with Music playing and an occasional jump to Gmail.
I'm running CM 3.9 with a simple Compcache script (no backing swap) initiated from Gscript for default disk size and 20 swappiness:
Code:
2.6.29-cm
12:23:08 up 36 min, load average: 3.37, 3.65, 2.79
20
Filename Type Size Used Priority
/dev/ramzswap0 partition 24464 6992 -1
DiskSize: 24468 kB
NumReads: 587
NumWrites: 1761
FailedReads: 0
FailedWrites: 0
InvalidIO: 0
PagesDiscard: 0
ZeroPages: 126
GoodCompress: 66 %
NoCompress: 5 %
PagesStored: 1635
PagesUsed: 602
OrigDataSize: 6540 kB
ComprDataSize: 2338 kB
MemUsedTotal: 2408 kB
total used free shared buffers
Mem: 97876 92880 4996 0 552
Swap: 24464 6992 17472
Total: 122340 99872 22468
Browser: N
total used free shared buffers
Mem: 97876 92856 5020 0 552
Swap: 24464 6992 17472
Total: 122340 99848 22492
Home: N
total used free shared buffers
Mem: 97876 92856 5020 0 552
Swap: 24464 6992 17472
Total: 122340 99848 22492
(after stressing with Music playing AND switching to Gmail)
Browser: Y
total used free shared buffers
Mem: 97876 95752 2124 0 452
Swap: 24464 7892 16572
Total: 122340 103644 18696
Home: N
total used free shared buffers
Mem: 97876 96496 1380 0 444
Swap: 24464 8276 16188
Total: 122340 104772 17568
ei8htohms said:
I ran this test with just Calendar and Weather widgets running on the home screen and, although I have occasionally found the entire home screen slow to reload during regular use, during this test the home screen never seemed to reload at all, even with Music playing and an occasional jump to Gmail.
Click to expand...
Click to collapse
And it probably doesn't, with compcache you have enough memory to keep it in, while without it needs to go through the whole onCreate and xml inflation.
I am not saying don't make it better. What I am saying is your expectations should be correct.
I use compcache myself. I use it with memlimit_kb=32000 disksize_kb=48000 backing_swap=/dev/block/mmcblk0p3 and a swappiness of 20. But I don't expect it to make my system fly. I just expect that more of my apps will stick around rather than killed and reloaded later. So, I am paying a little swapping cost upfront for payback later.
any lag once compcache fills up?
devsk said:
I am not saying don't make it better. What I am saying is your expectations should be correct.
I use compcache myself. I use it with memlimit_kb=32000 disksize_kb=48000 backing_swap=/dev/block/mmcblk0p3 and a swappiness of 20. But I don't expect it to make my system fly. I just expect that more of my apps will stick around rather than killed and reloaded later. So, I am paying a little swapping cost upfront for payback later.
Click to expand...
Click to collapse
Understood about managing expectations. I'm still considering the potential negative impact on battery life as well, since this is one notorious weak spot on the G1 (when it came out you didn't hear huge numbers of people complaining about how SLOW it was, but everyone complained about battery life...).
Do you mind explaining a little about your memlimit and disksize settings? I read a little about those options in the Google Code page, but I can't say I fully grokked the significance or difference.
I also can't seem to find a good explanation of how compcache and backing-swap work together. Most reports on XDA point to massive lag after compcache maxes out, but is it only then that backing-swap kicks in (and maybe a lot of those folks were using the 60 or 100 swappiness settings)? Can Linux-swap and compcache be run in parallel or separately from each other in some way (I'm guessing no)?
ei8htohms said:
Understood about managing expectations. I'm still considering the potential negative impact on battery life as well, since this is one notorious weak spot on the G1 (when it came out you didn't hear huge numbers of people complaining about how SLOW it was, but everyone complained about battery life...).
Do you mind explaining a little about your memlimit and disksize settings? I read a little about those options in the Google Code page, but I can't say I fully grokked the significance or difference.
I also can't seem to find a good explanation of how compcache and backing-swap work together. Most reports on XDA point to massive lag after compcache maxes out, but is it only then that backing-swap kicks in (and maybe a lot of those folks were using the 60 or 100 swappiness settings)? Can Linux-swap and compcache be run in parallel or separately from each other in some way (I'm guessing no)?
Click to expand...
Click to collapse
According to the Dev:
**********************************************************
Usage:
- modprobe ramzswap [memlimit_kb=<val>|disksize_kb=<val>] [backing_swap=<dev>]
memlimit_kb: This param is applicable only when backing_swap is given.
It is limit on amount compressed data stored in memory. Any
additional data is forwarded to backing_swap. It cannot be greater
than backing device size. If missing or 0, default value is used:
15% of RAM or backing device size, whichever is smaller.
disksize_kb: This param is applicable only when backing_swap is not given.
It is limit on amount of *uncompressed* worth of data stored in
memory. For e.g. disksize_kb=1024 means it can hold 1024kb worth of
uncompressed data even if this data compresses to just, say, 100kb.
If missing or 0, default value is used: 25% of RAM.
backing_swap: This is block device to be used as backing store for ramzswap.
It must be a valid swap partition. We move data to this device when we
encounter incompressible page or memlimit is reached. TODO: we may also
move some pages from ramzswap to this device in case system is really
low on memory.
This device is not directly visible to kernel as a swap device
(/proc/swaps will only show /dev/ramzswap0 and not this device).
Managing this backing device is the job of ramzswap module.
Examples:
1) modprobe ramzswap memlimit_kb=10240 backing_swap=/dev/sda2
sets ramzswap limit as 10MB and /dev/sda2 as backing swap device.
NOTE: here /dev/sda2 is a valid swap partition.
2) modprobe ramzswap backing_swap=/dev/sda2
same as (1) but memlimit is set to default: 15% of RAM or size of
backing swap device, whichever is smaller.
3) modprobe ramzswap disksize_kb=10240
sets ramzswap disk size as 10MB.
4) modprobe ramzswap.ko
same as (3) but ramzswap disk size will be set to default:
25% of RAM size.
Once module is loaded, activate this swap with highest priority:
swapon /dev/ramzswap0 -p 100
(-p param set swap priority)
Notes:
- ramzswap stats are exported via /proc/ramzswap
- If you give non-swap partition as backing_swap, nothing bad will happen -
swapon will simply fail to recognize /dev/ramzswap0 as swap partition.
So, in this case, unload the module and reload with correct backing_swap.
**********************************************************
thanks! very interesting
uwonsum said:
According to the Dev:
memlimit_kb: applicable only when backing_swap is given...limit on amount compressed data stored...additional data is forwarded to backing_swap.
disksize_kb: applicable only when backing_swap is not given...limit on amount of *uncompressed* worth of data stored.
Click to expand...
Click to collapse
So if I'm reading this right, memlimit and disksize would never be used together, right? And when backing_swap is NOT used, compcache is using the disksize allocation for uncompressed data, like virtual swap within RAM? Huh?
Once module is loaded, activate this swap with highest priority:
swapon /dev/ramzswap0 -p 100
(-p param set swap priority)
Click to expand...
Click to collapse
This swap priority info seems to directly conflict the info on the CompilingAndUsing page of the Google code project page:
Add ramzswap as swap device
swapon /dev/ramzswap0 -p 1 (give this swap device the highest priority).
Click to expand...
Click to collapse
Is 1 the highest priority or is 100 the highest priority? Is this the same as setting the swappiness? There must be a typo somewhere. Any help?
[EDIT]NVM, "-p 1" seems to be an invalid parameter.[/EDIT]
BTW, I started playing with your (rather more exotic) script from the CM Wheel of Death thread:
http://forum.xda-developers.com/showpost.php?p=4205132&postcount=518
Have you had any further findings about the various settings employed?
Thanks again!
In search of THE fastest ROM
SPACE SAVED FOR THE FASTEST ROM
Any help would be brilliant....
Im using SoftWeg Benchmark and would like anyone to download this after they have updated a ROM, Remove SD Card and wipe data. THEN do the Benchmark.
Cyanogenmod 3.9.8 32B
Graphics
Total graphics score;138.12605
Draw opacity bitmap;63.015385;MPixels per sec
Draw transparent bitmap;21.467505;MPixels per sec
CPU Whetstone
Total CPU score;132.67729
MWIPS DP;9.835743;MWIPS(DP)
MWIPS SP;9.461633;MWIPS(SP)
MFLOPS DP;2.0456715;MFLOPS(DP)
MFLOPS SP;1.7234094;MFLOPS(SP)
VAX MIPS DP;7.2467813;VAX MIPS(DP)
VAX MIPS SP;6.5513473;VAX MIPS(SP)
Memory
Total memory score;107.05253
Copy memory;97.27627;Mb/sec
Filesystem
Total file system score;21.418842
Creating 1000 empty files;8.866;sec
Deleting 1000 empty files;5.665;sec
Write 1M into file;2.107926;M/sec
Read 1M from file;40.98361;sM/sec;
SD card perfomance
Creating 250 empty files;11.292;sec
Deleting 250 empty files;7.876;sec
Write 1M into file;18.726591;M/sec
Read 1M from file;62.1118;sM/sec;
CyanogenMOD 3.9.9.1 32B
Graphics
Total graphics score;134.97528
Draw opacity bitmap;60.952385;MPixels per sec
Draw transparent bitmap;21.603376;MPixels per sec
CPU Whetstone
Total CPU score;166.22795
MWIPS DP;11.572734;MWIPS(DP)
MWIPS SP;12.675879;MWIPS(SP)
MFLOPS DP;2.2157722;MFLOPS(DP)
MFLOPS SP;3.0254915;MFLOPS(SP)
VAX MIPS DP;8.253114;VAX MIPS(DP)
VAX MIPS SP;8.443693;VAX MIPS(SP)
Memory
Total memory score;126.29102
Copy memory;114.75786;Mb/sec
Filesystem
Total file system score;31.679878
Creating 1000 empty files;7.051;sec
Deleting 1000 empty files;4.865;sec
Write 1M into file;2.0068233;M/sec
Read 1M from file;61.728394;sM/sec;
SD card perfomance
Creating 250 empty files;9.96;sec
Deleting 250 empty files;8.48;sec
Write 1M into file;19.607843;M/sec
Read 1M from file;67.1141;sM/sec;
Cyanogen 3.9.8 Sapphire Port - repacked 32B
Removed some apk's i dont use installed some i do..
Removed
Terminal Emulator
Quickoffice
Teeter
Android Log Viewer
Work Email
Email
Installed
Bluetooth Fileshare - Bluex
Taskiller Full
Screenshot
Graphics
Total graphics score;139.15968
Draw opacity bitmap;63.60248;MPixels per sec
Draw transparent bitmap;21.512606;MPixels per sec
CPU Whetstone
Total CPU score;171.2241
MWIPS DP;12.309206;MWIPS(DP)
MWIPS SP;12.81887;MWIPS(SP)
MFLOPS DP;2.204739;MFLOPS(DP)
MFLOPS SP;3.123229;MFLOPS(SP)
VAX MIPS DP;8.649143;VAX MIPS(DP)
VAX MIPS SP;8.469682;VAX MIPS(SP)
Memory
Total memory score;131.08994
Copy memory;119.11852;Mb/sec
Filesystem
Total file system score;31.62359
Creating 1000 empty files;7.521;sec
Deleting 1000 empty files;5.127;sec
Write 1M into file;1.8935808;M/sec
Read 1M from file;61.728394;sM/sec;
SD card perfomance
Creating 250 empty files;9.872;sec
Deleting 250 empty files;7.904;sec
Write 1M into file;20.325203;M/sec
Read 1M from file;62.89308;sM/sec;
Free'd up some space and got minor performance changes..
Nice. Would love to seem more. How about putting them in Excel for easier comparing?
What program are you using to get the performance tests...
I would like to post TMO MyHero (Touch...) with the Fata1ity Hero Rom.
using benchmark by softweg from the market.Try to make sure there isnt too many applications allready on the phone,i would move dalvik cache and apps to sd first
When i have enough results i will put it all into an excel spreadsheet
a quick run on the JACxHERO1.2x on a 32A
Graphics
Total graphics score;110.75547
Draw opacity bitmap;56.7313;MPixels per sec
Draw transparent bitmap;11.010753;MPixels per sec
CPU Whetstone
Total CPU score;157.20335
MWIPS DP;11.52605;MWIPS(DP)
MWIPS SP;11.429877;MWIPS(SP)
MFLOPS DP;1.8925545;MFLOPS(DP)
MFLOPS SP;3.1283667;MFLOPS(SP)
VAX MIPS DP;7.8506227;VAX MIPS(DP)
VAX MIPS SP;7.851712;VAX MIPS(SP)
Memory
Total memory score;126.917305
Copy memory;115.32695;Mb/sec
Filesystem
Total file system score;25.252697
Creating 1000 empty files;6.779;sec
Deleting 1000 empty files;4.526;sec
Write 1M into file;1.7850767;M/sec
Read 1M from file;49.019608;sM/sec;
SD card perfomance
Creating 250 empty files;12.788;sec
Deleting 250 empty files;7.024;sec
Write 1M into file;10.080646;M/sec
Read 1M from file;50.76142;sM/sec;
CyanogenMOD 3.9.10 One ROM for all 32B
Graphics
Total graphics score;141.94427
Draw opacity bitmap;64.605675;MPixels per sec
Draw transparent bitmap;22.212582;MPixels per sec
CPU Whetstone
Total CPU score;156.0196
MWIPS DP;11.32631;MWIPS(DP)
MWIPS SP;11.868028;MWIPS(SP)
MFLOPS DP;2.2806008;MFLOPS(DP)
MFLOPS SP;2.943571;MFLOPS(SP)
VAX MIPS DP;7.775884;VAX MIPS(DP)
VAX MIPS SP;7.155885;VAX MIPS(SP)
Memory
Total memory score;126.50879
Copy memory;114.95574;Mb/sec
Filesystem
Total file system score;31.797188
Creating 1000 empty files;8.394;sec
Deleting 1000 empty files;6.149;sec
Write 1M into file;1.8594273;M/sec
Read 1M from file;62.1118;sM/sec;
SD card perfomance
Creating 250 empty files;11.772;sec
Deleting 250 empty files;7.812;sec
Write 1M into file;19.96008;M/sec
Read 1M from file;62.89308;sM/sec;
Thanks chris B, I thought the 32A has more memory? Seems strange its score is no better on the memory test :/
bonesy said:
Thanks chris B, I thought the 32A has more memory? Seems strange its score is no better on the memory test :/
Click to expand...
Click to collapse
Let me just flash the Cyanogen 3.9.9.1 and do a bench..
ChrisB said:
Let me just flash the Cyanogen 3.9.9.1 and do a bench..
Click to expand...
Click to collapse
Thanks i have to work now so will put all the info so far into a spreadsheet or some sort of graph when i get back at 1am.Thanks again and please keep them coming its not a particularly hard thing to do!
Here we go.. CyanogenMOD 3.9.9.1 32A port.
Graphics
Total graphics score;122.895775
Draw opacity bitmap;53.472584;MPixels per sec
Draw transparent bitmap;21.694916;MPixels per sec
CPU Whetstone
Total CPU score;163.58177
MWIPS DP;11.648224;MWIPS(DP)
MWIPS SP;12.211503;MWIPS(SP)
MFLOPS DP;2.2989812;MFLOPS(DP)
MFLOPS SP;3.1188185;MFLOPS(SP)
VAX MIPS DP;7.918034;VAX MIPS(DP)
VAX MIPS SP;8.255877;VAX MIPS(SP)
Memory
Total memory score;126.946594
Copy memory;115.35356;Mb/sec
Filesystem
Total file system score;28.689903
Creating 1000 empty files;7.56;sec
Deleting 1000 empty files;5.23;sec
Write 1M into file;1.8539118;M/sec
Read 1M from file;55.86592;sM/sec;
SD card perfomance
Creating 250 empty files;35.272;sec
Deleting 250 empty files;7.028;sec
Write 1M into file;18.083183;M/sec
Read 1M from file;57.471264;sM/sec;
Cyanogen 3.9.11.2 32B
Graphics
Total graphics score;140.79968
Draw opacity bitmap;65.431305;MPixels per sec
Draw transparent bitmap;20.686869;MPixels per sec
CPU Whetstone
Total CPU score;160.76784
MWIPS DP;11.17568;MWIPS(DP)
MWIPS SP;12.397718;MWIPS(SP)
MFLOPS DP;2.22978;MFLOPS(DP)
MFLOPS SP;3.0210845;MFLOPS(SP)
VAX MIPS DP;7.9092903;VAX MIPS(DP)
VAX MIPS SP;7.9360266;VAX MIPS(SP)
Memory
Total memory score;121.46799
Copy memory;110.375275;Mb/sec
Filesystem
Total file system score;18.566294
Creating 1000 empty files;9.154;sec
Deleting 1000 empty files;4.861;sec
Write 1M into file;2.0169423;M/sec
Read 1M from file;35.33569;sM/sec;
SD card perfomance
Creating 250 empty files;18.232;sec
Deleting 250 empty files;7.98;sec
Write 1M into file;0.024713753;M/sec
Read 1M from file;67.567566;sM/sec;
I did a benchmark using superlight themed Hero but results were far too low to compare. Got 67.9 graphics and 108 cpu.
When i have enough i will host an excel report with graphs and stuff.
BEST SO FAR!!!
OMG LOOK AT THE CPU IN THIS ROM AMON RA V1.1 32A
Graphics
Total graphics score;115.16564
Draw opacity bitmap;56.7313;MPixels per sec
Draw transparent bitmap;13.708165;MPixels per sec
CPU Whetstone
Total CPU score;180.01723
MWIPS DP;13.140604;MWIPS(DP)
MWIPS SP;13.730605;MWIPS(SP)
MFLOPS DP;2.2668297;MFLOPS(DP)
MFLOPS SP;3.1103702;MFLOPS(SP)
VAX MIPS DP;8.962355;VAX MIPS(DP)
VAX MIPS SP;8.807292;VAX MIPS(SP)
Memory
Total memory score;127.10787
Copy memory;115.500114;Mb/sec
Filesystem
Total file system score;30.420616
Creating 1000 empty files;7.808;sec
Deleting 1000 empty files;5.145;sec
Write 1M into file;1.3215277;M/sec
Read 1M from file;59.88024;sM/sec;
SD card perfomance
Creating 250 empty files;8.116;sec
Deleting 250 empty files;6.108;sec
Write 1M into file;22.172949;M/sec
Read 1M from file;60.97561;sM/sec;
Thanks killa, I think im going to need 2 seperate reports when we've compiled enough info. 1 for 32A and 1 For 32B.It seems that 32A gets alot more cpu than b.Out of curiosity are you both using an overclocking application?
yup setcpu 528/384
Killadude said:
yup setcpu 528/384
Click to expand...
Click to collapse
Brilliant im doing the same but with overclock widget. For some reason setCPU would revert to defaults when i went to home screen.
have u tried the latest version 1.3.6?
ps the reason my sd is slow is cuz its not class 6!
I think ill leave sd out as the result will vary the most
Just looking for input on the fastest ROM out there. I've only tried one myself - MightyROM - and I love it, but I do get a frustrating amount of lag on the phone and tends to use alot of RAM.
What are your lightning fast fav's?
I really liked the bare naked ROM series but that was discontinued, hands down it was the fastest ROM i've ever tried. Right now i honestly cant find any noticable difference between most ROMS anymore in terms of speed. Although I havnt tried grooveROM, I just overclock all my ROMS now and any manila 2.5 ROM is almost always the same speed.
I have used alot of roms but so far the one I have kept the longest is the neodium rom. Get the one that says "Sept 15 Neo-CHT-2018 (SYS 21916)". Manila runs so smooth, it has CHT, & I have never had any lock ups. I haven't soft reset my phone in about 1 month (which is when I got the rom). That says it all to me.
Here is the link at PPCGeeks.
Thanks for the info. I think I'll give that other rom a try. I hadn't considered overclocking but I'll start a seach for that and see how thats done too. Thanks!
Loaded neodium rom last night and so far really like it. It really does seem faster! Have you tried the other versions of it that are available - Plutonium?
Mine is 21057 core WM 6.1 with Sense 2.1919,that is freaking fast enough,and always stay on around 50% RAM,that's why I don't like any WM 6.5 with Sense 2.5 till now
Please people. If you are gonna say that any rom is the "fastest", please post benchmarks to prove it.
Benchmarks from my latest rom:
Code:
Report
Spb Benchmark Indices
Spb Benchmark index 541.81 (iPAQ 3650 scored 1000)
CPU index 2397.32 (iPAQ 3650 scored 1000)
File system index 227.01 (iPAQ 3650 scored 1000)
Graphics index 1709.62 (iPAQ 3650 scored 1000)
ActiveSync index insufficient number of tests were done. (iPAQ 3650 scored 1000)
Platform index insufficient number of tests were done. (iPAQ 3650 scored 1000)
Main test was not done
Main test results
Test Time Speed % of iPAQ 3650* speed
Write 1 MB file 458 ms 2238 KB/sec 282%
Read 1 MB file 56.4 ms 17.7 MB/sec 97%
Copy 1 MB file 507 ms 2020 KB/sec 256%
Write 10 KB x 100 files 4197 ms 244 KB/sec 44%
Read 10 KB x 100 files 338 ms 2.96 MB/sec 47%
Copy 10 KB x 100 files 3998 ms 256 KB/sec 54%
Directory list of 2000 files 1024 ms 1.95 thousands of files/sec 2%
Internal database read 621 ms 1610 records/sec 382%
Graphics test: DDB BitBlt 11.4 ms 88 frames/sec 327%
Graphics test: DIB BitBlt 28.5 ms 35.1 frames/sec 260%
Graphics test: GAPI BitBlt 4.47 ms 223 frames/sec 104%
Compress 1 MB file using ZIP 2396 ms 423 KB/sec 399%
Decompress 1024x768 JPEG file 499 ms 564 KB/sec 177%
Arkaball frames per second 6.81 ms 147 frames/sec 136%
CPU test: Whetstones MFLOPS 2771 ms 0.134 Mop/sec 291%
CPU test: Whetstones MOPS 814 ms 77.4 Mop/sec 227%
CPU test: Whetstones MWIPS 5820 ms 8.59 Mop/sec 289%
Memory test: copy 1 MB using memcpy 6.82 ms 147 MB/sec 208%
MR.X ROM its super fast but you cant send picture mail
The Energy Titanium ROM is the fastest so far and the least number of problems! Very silky smooth.
Hi all! I am looking for a confirmation of a storage speed. I did test the display unit in T-Mobile store yesterday, but the score seemed very low/slow. So I did "macro" test pass using Androbench 5 app and the upper 2 scores were ~ 280MB/s as the reading speed and writing speed was ~ 130MB/s. I just don't remember the rest. I believe there could something be wrong with the device, the app or the OS. The device felt fast and updated/installed apps as fast as the big U11 does. If any of you have this device on hand, could you please test the "macro" speed and report?
I just ran this on my HTC U11 Life, here're the results:
Sequential Read: 265.77 MB/s
Sequential Write: 122.4 MB/s
Random Read: 42.87 MB/s, 10977.16 IOPS (4KB)
Random Write: 35.81 MB/s, 9169.41 IOPS (4KB)
SQLite Insert: 1715.8.8 QPS, 0.75 sec
SQLite Update: 2575.48 QPS, 0.79 sec
SQLite Delete: 4751.52 QPS, 0.43 sec
Is this the thing for which you were looking?
edit: formatting
iamxaq said:
I just ran this on my HTC U11 Life, here're the results:
Sequential Read: 265.77 MB/s
Sequential Write: 122.4 MB/s
Random Read: 42.87 MB/s, 10977.16 IOPS (4KB)
Random Write: 35.81 MB/s, 9169.41 IOPS (4KB)
SQLite Insert: 1715.8.8 QPS, 0.75 sec
SQLite Update: 2575.48 QPS, 0.79 sec
SQLite Delete: 4751.52 QPS, 0.43 sec
Is this the thing for which you were looking?
edit: formatting
Click to expand...
Click to collapse
That is all I needed! Thanks!
To confirm, I've not had any issues with lag or lack of responsiveness to this point; however, the context of 'I am coming from a Nexus 5 that was 4 years old' matters, so I am far from an impartial observer.