My small question: what is needed to download NEON version? Boinc client from NativeBOINC uses 'arm-android' and 'arm-android-linux-gnu' platforms.
Thanks your for any help.
Version 1.02 works very well on my smartphone with Nativeboinc :)
It was configured to only be shipped to version 7.1.0 and above of BOINC client (for tests of an Android client that is part of the official BOINC repo now.
For now I set this back to 7.0.36 ,so ARMv7 NEON BRP4U should be usable with NativeBOINC now, but again, this might change w/o notice :-).
Also expect a new ARMv6 version in the near future.
Happy to see what's going on here!
I've set pogs to no new tasks and hope to get one of the arm7 wu's next time a wu is requested.
For now my Nexus (running in Dock, set to use 2 CPU's) crunches a 'single DM'. Now it has reached 32% after 24 hours.
Happy to see what's going on here!
I've set pogs to no new tasks and hope to get one of the arm7 wu's next time a wu is requested.
For now my Nexus (running in Dock, set to use 2 CPU's) crunches a 'single DM'. Now it has reached 32% after 24 hours.
Sounds about right. The NEON version should be almost 4 times faster than this one. Even the ARMv6 version (after the latest update) should be almost twice as fast as the old ARMv6 version you are using now....hopefully.
I've got one 1.03 this night. After ~4hrs of crunching 30% are done. Great app! In about 3 hrs it will overtake the 1.02 app, which is currently @50% after 37 hrs.
Which brings up the question whether it is worthwhile to support non-NEON Android devices at all.
I'd like to hear feedback on this question. Are there enough old or low-end Android devices with ARMv6 CPUs around ??? Would volunteers care to run tasks on them that take (say) between 2 and 3 CPU days to complete (so, say, 6 to 9 days of elapsed time if you crunch 8 hours per day (or most likely night :-) )???
If there is sufficient demand we will provide this support, if not, dropping ARMv6-android will reduce pending tasks for the others (less waiting for very slow devices). Thoughts?
Cheers
HB
P.S.: FWIW, the RaspberryPi also doesn't support NEON, but OTOH it makes up for it by (usually) running under Raspbian, a Debian Linux port that uses the so called Hard-float ABI ==> better floating point performance for the same hardware when compared to Android's "soft(fp)" ABI. So the Raspi BRP4U performance seems to be somewhere in between the Android ARMv6 (VFP) and ARMv7 (NEON) app version performance. And it's easier to have a Raspi running 24/7 connected to mains than a phone that will most likely only crunch while connected to a charger.
Which brings up the question whether it is worthwhile to support non-NEON Android devices at all.
Speaking for myself only - no. Encouraged by the excellent performance of the 1.03 app (finished in 12h 50min) on my Nexus I installed the app also on my smartphone; got one 1.03 as well. Let's see how it acts with the setting run on charger only.
Quote:
I'd like to hear feedback on this question. Are there enough old or low-end Android devices with ARMv6 CPUs around ??? Would volunteers care to run tasks on them that take (say) between 2 and 3 CPU days to complete (so, say, 6 to 9 days of elapsed time if you crunch 8 hours per day (or most likely night :-) )???
I have no such devices.
Quote:
If there is sufficient demand we will provide this support, if not, dropping ARMv6-android will reduce pending tasks for the others (less waiting for very slow devices). Thoughts?
it might take longer to wait for the wingman, but it does not change the outcome (assuming the results will be the same ...)
Quote:
Cheers
HB
P.S.: FWIW, the RaspberryPi also doesn't support NEON, but OTOH it makes up for it by (usually) running under Raspbian, a Debian Linux port that uses the so called Hard-float ABI ==> better floating point performance for the same hardware when compared to Android's "soft(fp)" ABI. So the Raspi BRP4U performance seems to be somewhere in between the Android ARMv6 (VFP) and ARMv7 (NEON) app version performance. And it's easier to have a Raspi running 24/7 connected to mains than a phone that will most likely only crunch while connected to a charger.
I agree, so it looks like it will make sense to support it. There are many, many of them out there! But someone with contact to this scene needs to make some advertising for this project in serveral Raspberry foras.
Yesterday i ran the 1.02 app on my armv6 mobile phone (galaxy mini gts 5570)and i have determined that it took 20h for crunching 10% of the work.
After that i read here on the forum that the NEON app 1.03 is available here for that type of processor and i (sorry)aborted the task.
But what i can see now in crunching time is that with the 1.03 app it takes a little less then 1h to crunch 1% so i have done with that phone in 20h 20 ore more then 20 percentage of the task so it´s how you said Bikeman.
The armv6 runs with doubled speed with this NEON app instead of app 1.02
For those who run not 24/7 that´s a good thing to be not behind the deadline.
But no idea how much user will crunch on this type of processor because there are many newer on the market.
What i know for sure, there are sure people who don´t want to crunch on there newest Phone because its high price let me say of 300 or 500Euro for a good device or more.
That´s not small for a phone.
I think it´s the same if you put a high end pc together and crunch on that.
But i think you have to see that on the live servers how that develops.
I forgot to say
Another thing what you could do is to ask google how much android arm v6 devices they have actually contact with (percentage of all devices) on the Internet :)
But i don´t know if they give you an answer.
Or perhaps you find a good statistic over that on a reliable news website.
The release dates of them and the processor achitecture which you can find if you click on the System on chip entries could perhaps help to make a decision.
Thanks for the bug
)
Thanks for the bug report
It was configured to only be shipped to version 7.1.0 and above of BOINC client (for tests of an Android client that is part of the official BOINC repo now.
For now I set this back to 7.0.36 ,so ARMv7 NEON BRP4U should be usable with NativeBOINC now, but again, this might change w/o notice :-).
Also expect a new ARMv6 version in the near future.
Cheers
HB
Happy to see what's going on
)
Happy to see what's going on here!
I've set pogs to no new tasks and hope to get one of the arm7 wu's next time a wu is requested.
For now my Nexus (running in Dock, set to use 2 CPU's) crunches a 'single DM'. Now it has reached 32% after 24 hours.
RE: Happy to see what's
)
Sounds about right. The NEON version should be almost 4 times faster than this one. Even the ARMv6 version (after the latest update) should be almost twice as fast as the old ARMv6 version you are using now....hopefully.
Cheers
HB
I've got one 1.03 this night.
)
I've got one 1.03 this night. After ~4hrs of crunching 30% are done. Great app! In about 3 hrs it will overtake the 1.02 app, which is currently @50% after 37 hrs.
Which brings up the question
)
Which brings up the question whether it is worthwhile to support non-NEON Android devices at all.
I'd like to hear feedback on this question. Are there enough old or low-end Android devices with ARMv6 CPUs around ??? Would volunteers care to run tasks on them that take (say) between 2 and 3 CPU days to complete (so, say, 6 to 9 days of elapsed time if you crunch 8 hours per day (or most likely night :-) )???
If there is sufficient demand we will provide this support, if not, dropping ARMv6-android will reduce pending tasks for the others (less waiting for very slow devices). Thoughts?
Cheers
HB
P.S.: FWIW, the RaspberryPi also doesn't support NEON, but OTOH it makes up for it by (usually) running under Raspbian, a Debian Linux port that uses the so called Hard-float ABI ==> better floating point performance for the same hardware when compared to Android's "soft(fp)" ABI. So the Raspi BRP4U performance seems to be somewhere in between the Android ARMv6 (VFP) and ARMv7 (NEON) app version performance. And it's easier to have a Raspi running 24/7 connected to mains than a phone that will most likely only crunch while connected to a charger.
RE: Which brings up the
)
Speaking for myself only - no. Encouraged by the excellent performance of the 1.03 app (finished in 12h 50min) on my Nexus I installed the app also on my smartphone; got one 1.03 as well. Let's see how it acts with the setting run on charger only.
I have no such devices.
it might take longer to wait for the wingman, but it does not change the outcome (assuming the results will be the same ...)
I agree, so it looks like it will make sense to support it. There are many, many of them out there! But someone with contact to this scene needs to make some advertising for this project in serveral Raspberry foras.
Yesterday i ran the 1.02 app
)
Yesterday i ran the 1.02 app on my armv6 mobile phone (galaxy mini gts 5570)and i have determined that it took 20h for crunching 10% of the work.
After that i read here on the forum that the NEON app 1.03 is available here for that type of processor and i (sorry)aborted the task.
But what i can see now in crunching time is that with the 1.03 app it takes a little less then 1h to crunch 1% so i have done with that phone in 20h 20 ore more then 20 percentage of the task so it´s how you said Bikeman.
The armv6 runs with doubled speed with this NEON app instead of app 1.02
For those who run not 24/7 that´s a good thing to be not behind the deadline.
But no idea how much user will crunch on this type of processor because there are many newer on the market.
What i know for sure, there are sure people who don´t want to crunch on there newest Phone because its high price let me say of 300 or 500Euro for a good device or more.
That´s not small for a phone.
I think it´s the same if you put a high end pc together and crunch on that.
But i think you have to see that on the live servers how that develops.
That´s my personally estimation of this.
I forgot to say Another
)
I forgot to say
Another thing what you could do is to ask google how much android arm v6 devices they have actually contact with (percentage of all devices) on the Internet :)
But i don´t know if they give you an answer.
Or perhaps you find a good statistic over that on a reliable news website.
What i could find on the
)
What i could find on the Internet is this comparison of android devices
http://en.wikipedia.org/wiki/Comparison_of_Android_devices
The release dates of them and the processor achitecture which you can find if you click on the System on chip entries could perhaps help to make a decision.
I installed that app
)
I installed that app yesterday on my HTC Desire X as well, got one 1.03 task.
Runtime until now is 13:29:15, 77,18% done.
This is a 250€ phone.