Message boards :
Number crunching :
Multicore smartphones - how to use their full potential
Message board moderation
Previous · 1 · 2 · 3
Author | Message |
---|---|
Jord Send message Joined: 9 Jun 99 Posts: 15184 Credit: 4,362,181 RAC: 3 |
Direct comparison. Task https://setiathome.berkeley.edu/result.php?resultid=6236351563 run time 225,892.29 CPU time 103,635.70 Task https://setiathome.berkeley.edu/result.php?resultid=6236425769 run time 227,298.17 CPU time 103,882.20 Not even going to do the ratios, you can see these are slower. Also armv7-vfpv3-nopie, but this time run with the display off. CPU temp as far as I saw, 30 - 35C. |
Pierre A Renaud Send message Joined: 3 Apr 99 Posts: 998 Credit: 9,101,544 RAC: 65 |
3 weeks l8r, on my Samsung TAB E tablet, my average turnaround time of 1.38 days increased to 1.52 and on my Polaroid A4 smarthone it increased from 2.23 to 2.96. I'll uninstall the apps shortly, since they are not improving things and aren't apparently forcing the devices in high-power state. I should have controlled for WU types, but considering the low stakes involved and the short 3 week trial period, I chose not to bother with that. I will test Keep Screen On for my aging Polaroid A4 android smartphone, which can disable my maximum imposed 30 minutes screen saver time (No Screen Off is simple to use, but can't bypass the 30 minutes imposed limit). In a week or two I'll be able to see if it can significantly improve on my Average turnaround time of 2.23 days. Apr 3, 1999 - May 3, 2020 |
Karl Öberg Send message Joined: 8 Jun 99 Posts: 16 Credit: 37,577,764 RAC: 230 |
How did it go? |
Pierre A Renaud Send message Joined: 3 Apr 99 Posts: 998 Credit: 9,101,544 RAC: 65 |
How did it go?Not good: for my TAB E Samsung tablet, the daily WU output decreased by 10%, and for the Polaroid A4 smartphone it decreased it by 33%. The Android app retained for both was Keep Screen On (No Screen Off could not prevent the A4's screen from going blank after 30 mins). Allowing their screens to turn off then probably insures that more ressources can be allocated to the SETI@home app without activating (or more than compensating) a sleep mode thought to be significantly detrimental to the SETI@home app's performance - at least for these mobile models. I'm glad to report that all devices have now been returned intact to their standardized space-time fishy continuums. Apr 3, 1999 - May 3, 2020 |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.