I just completed my first task for Asteroids @ home, but it took a whopping 59 hours. For Android, is that too long?

I just completed my first task for Asteroids @ home, but it took a whopping 59 hours. For Android, is that too long?

It validated so not too long for the project, but it does show how inefficient the ARM processor can be. What else were you doing with it while it was crunching? Did you leave it plugged in the whole time?

It was just sitting there plugged in. It's probably just because it's a fairly cheap phone, even though I've overclocked it. I was just curious because WCG tasks rarely take more than 16 hours so I thought 59 was maybe too much for this. If that's so, then that's fine. :)

What is the average time for these tasks on Android?

---

What is the average time for these tasks on Android?

Unless you find another user I don't have a clue how to find out.

What is the average time for these tasks on Android?

What is the average time for these tasks on Windows
What is the average time for these tasks on Linux

(if you see any sense in the above questions I don't)

The question is:
What is the average time for these tasks on "ARMv7 Processor rev 1 (v7l)" / Android
(what MHz is this CPU I don't know)
http://asteroidsathome.net/boinc/show_host_detail.php?hostid=170125


I just go to "Android 5 support" thread and check a few users that posted there:
http://asteroidsathome.net/boinc/forum_thread.php?id=419

ARMv7 Processor rev 0 (v7l)
http://asteroidsathome.net/boinc/show_host_detail.php?hostid=139298
http://asteroidsathome.net/boinc/results.php?hostid=139298&offset=0&show_names=0&state=4&appid=

ARMv7 Processor rev 2 (v7l)
http://asteroidsathome.net/boinc/show_host_detail.php?hostid=153180
http://asteroidsathome.net/boinc/results.php?hostid=153180&offset=0&show_names=0&state=4&appid=

---

- ALF - "Find out what you don't do well ..... then don't do it!" :)

My Samsung Tab 4 completed the last few with elapse times between 39-49 hrs. So your time doesn't seem too outlandish.
Points awarded would be decent for Andriod if they would post to Boincstats.

My Samsung Tab 4 completed the last few with elapse times between 39-49 hrs. So your time doesn't seem too outlandish.
Points awarded would be decent for Andriod if they would post to Boincstats.

You seem to have multiple accounts over time and pc's, when I look your name up in both Boincsats and FreeDC it comes up with multiple accounts for that name. Could they be accumulating on another account?

http://stats.free-dc.org/stats.php?page=search&proj=&team=&name=DadX&exact=N&cross=N

http://boincstats.com/en/stats/search/#DadX

I just completed my first task for Asteroids @ home, but it took a whopping 59 hours. For Android, is that too long?

I noticed these rather long times too in the last few weeks. There hasn't been any notes from Kyong though...

Let's break it down like this:

Let's say that we get a good 6 hours per day of computing in allowing for the charge to hit 90%...

60 hours / 6 hours/day = 10 days to complete

We're looking at about a 10 day deadline right now.

I have a couple of iRulu X1s that run at 1.4 Ghz. It takes 50+ hours for a WU.
My Fire HDX 8.9 runs at 2.2 GHz. I'm looking at around 30 hours for a WU (roughly 6 hours to reach 20%).

IIRC, Asteroids WAS running about 30 hours on my iRulus at the beginning of the month, so something changed, either the work or the algorithm that determines what work to send out...


I did get two very fast WUs last night. These were of "*input_18324..."

For slower devices, these would be quite nice. 50 - 60 hours is overkill.

Mine seems to do between 47 and 54 hours.
Results

---

I have an Nvidia Shield TV with the Tegra X1 and it takes about 10hours cpu time per unit on average.

Between 18 - 20 hours per WU on my Samsung Galaxy S5 SM-G900F, ARMv7 Processor rev 1 (v7l) Qualcomm Snapdragon 801 2.46GHz