How long does it take on Android?
log in

Advanced search

Message boards : Number crunching : How long does it take on Android?

Author Message
numbermaniac
Send message
Joined: 26 Jul 14
Posts: 30
Credit: 5,977,334
RAC: 12,924
Message 21636 - Posted: 30 Oct 2015, 11:43:17 UTC

So I got my first task on my phone today, but after nearly 7 hours it's only 2.5% complete. Is it supposed to take this long?!

Matt Kowal
Avatar
Send message
Joined: 21 Mar 14
Posts: 34
Credit: 674,222,805
RAC: 462,255
Message 21639 - Posted: 31 Oct 2015, 6:47:17 UTC

What android device do you have? Do you know the hardware specs?


I used to have an android device that ran the micro work units in a few hours. The new android sieve apps were added at the end of September, but I have yet to try those.

Profile mikey
Avatar
Send message
Joined: 11 Aug 09
Posts: 3242
Credit: 1,694,296,873
RAC: 5,408,507
Message 21640 - Posted: 31 Oct 2015, 10:49:24 UTC - in response to Message 21636.

So I got my first task on my phone today, but after nearly 7 hours it's only 2.5% complete. Is it supposed to take this long?!


Adjust the settings so it runs 100% of the time and runs whether it is charging or not and it should go faster. By default, when I ran some, they didn't run when not plugged in and the battery was below 90%, which happens pretty quickly when crunching. I ended up stopping running them because I didn't want to leave my tablet plugged in 24/7.

numbermaniac
Send message
Joined: 26 Jul 14
Posts: 30
Credit: 5,977,334
RAC: 12,924
Message 21643 - Posted: 1 Nov 2015, 0:17:56 UTC - in response to Message 21639.
Last modified: 1 Nov 2015, 0:20:35 UTC

What android device do you have? Do you know the hardware specs?


I used to have an android device that ran the micro work units in a few hours. The new android sieve apps were added at the end of September, but I have yet to try those.


Sony Xperia E, Android 4.1.1
Single core 1.8 GHz, (Qualcomm Snapdragon MSM7227A)
it's an ARM processor so i don't know if the micro units are enabled for it.
559 MB RAM (409 physical + 150 swap file)

You can also click on my username and look at my computer list to see my phone there.

numbermaniac
Send message
Joined: 26 Jul 14
Posts: 30
Credit: 5,977,334
RAC: 12,924
Message 21644 - Posted: 1 Nov 2015, 0:20:02 UTC - in response to Message 21640.

So I got my first task on my phone today, but after nearly 7 hours it's only 2.5% complete. Is it supposed to take this long?!


Adjust the settings so it runs 100% of the time and runs whether it is charging or not and it should go faster. By default, when I ran some, they didn't run when not plugged in and the battery was below 90%, which happens pretty quickly when crunching. I ended up stopping running them because I didn't want to leave my tablet plugged in 24/7.


I've allowed it to run on battery until it reaches 40%. The task is currently 15.8% complete after 38.3 hours. The fact that the workunit goes through 6.6 trillion numbers probably isn't a good thing.

Profile mikey
Avatar
Send message
Joined: 11 Aug 09
Posts: 3242
Credit: 1,694,296,873
RAC: 5,408,507
Message 21645 - Posted: 1 Nov 2015, 10:34:35 UTC - in response to Message 21644.

So I got my first task on my phone today, but after nearly 7 hours it's only 2.5% complete. Is it supposed to take this long?!


Adjust the settings so it runs 100% of the time and runs whether it is charging or not and it should go faster. By default, when I ran some, they didn't run when not plugged in and the battery was below 90%, which happens pretty quickly when crunching. I ended up stopping running them because I didn't want to leave my tablet plugged in 24/7.


I've allowed it to run on battery until it reaches 40%. The task is currently 15.8% complete after 38.3 hours. The fact that the workunit goes through 6.6 trillion numbers probably isn't a good thing.


I don't remember mine taking that long, more like one unit per day, but it's been a long time so yes the 16T size could be a problem. Mine was an ARM too and it ran the 'micro' units.

Dr Who Fan
Avatar
Send message
Joined: 27 May 14
Posts: 21
Credit: 4,562,054
RAC: 0
Message 21649 - Posted: 1 Nov 2015, 18:02:11 UTC

On my Nexus 7 tablet (ARMv7 Processor rev 9 (v7l) @1300MHz / Quad-Core) the new tasks (Collatz Sieve) will take approximately 193 HOURS of CPU time running at 100% CPU use.

Due the the battery starting to show it's age I have run the CPU's at aprox aprox 65% of full power, the task I have running now is estimated at aprox 300 hours of total run/computation time.
____________

numbermaniac
Send message
Joined: 26 Jul 14
Posts: 30
Credit: 5,977,334
RAC: 12,924
Message 21650 - Posted: 1 Nov 2015, 19:42:47 UTC - in response to Message 21645.

So I got my first task on my phone today, but after nearly 7 hours it's only 2.5% complete. Is it supposed to take this long?!


Adjust the settings so it runs 100% of the time and runs whether it is charging or not and it should go faster. By default, when I ran some, they didn't run when not plugged in and the battery was below 90%, which happens pretty quickly when crunching. I ended up stopping running them because I didn't want to leave my tablet plugged in 24/7.


I've allowed it to run on battery until it reaches 40%. The task is currently 15.8% complete after 38.3 hours. The fact that the workunit goes through 6.6 trillion numbers probably isn't a good thing.


I don't remember mine taking that long, more like one unit per day, but it's been a long time so yes the 16T size could be a problem. Mine was an ARM too and it ran the 'micro' units.


Unfortunately the task had an error overnight... oh well. I tried allowing only micro but it said no tasks available for micro.

numbermaniac
Send message
Joined: 26 Jul 14
Posts: 30
Credit: 5,977,334
RAC: 12,924
Message 21651 - Posted: 1 Nov 2015, 19:44:16 UTC - in response to Message 21649.

On my Nexus 7 tablet (ARMv7 Processor rev 9 (v7l) @1300MHz / Quad-Core) the new tasks (Collatz Sieve) will take approximately 193 HOURS of CPU time running at 100% CPU use.

Due the the battery starting to show it's age I have run the CPU's at aprox aprox 65% of full power, the task I have running now is estimated at aprox 300 hours of total run/computation time.


Yikes. So it's not just me then. Slicker, can we get the Android tasks a bit smaller? They shouldn't be expected to do the same amount of work as a desktop GPU :(

numbermaniac
Send message
Joined: 26 Jul 14
Posts: 30
Credit: 5,977,334
RAC: 12,924
Message 21652 - Posted: 2 Nov 2015, 7:08:35 UTC - in response to Message 21651.

If Android ARM could run Micro Collatz, like other Android types can, that'd probably solve a lot.

numbermaniac
Send message
Joined: 26 Jul 14
Posts: 30
Credit: 5,977,334
RAC: 12,924
Message 21656 - Posted: 2 Nov 2015, 22:33:45 UTC - in response to Message 21652.

I adjusted the preferences a few days ago and overnight my phone got a micro! Yay!


Post to thread

Message boards : Number crunching : How long does it take on Android?


Main page · Your account · Message boards


Copyright © 2018 Jon Sonntag; All rights reserved.