The rest of them have also knocked over one each (I have 5 Pi's on the job). They seem to be a consistent 31 hours and 35 to 40 minutes. Great job guys :-)
This long weekend I made some tests for speed comparison.
My old, retired Intel Atom 2x1.8GHz has seen a new spring. A clean win7 with actual Boinc Manager and a project which is availanble for both platforms and validating against each other.
Pogs.
My Nexus runs these apps in ~8 hrs, using 2 of the 4 cores it finishes ~6 wu's within 24 hrs.
The Atom is running 4 threads, for 16 hrs now. The fastest wu has reached now 64%, the slowest 41%. Even my phone is faster.
My i3 3220 needs ~6000 sec's/wu running 4 threads.
I think ARM, Parelela & Co are the future. In terms of speed, power consumption, amount of devices available and headroom for improvements.
All it needs is some advertising for arm-projects. They can easily replace the older laptops and desktops.
And the Atom? I think, the spring will end soon ...
I think it's too early for funeral eulogies wrt. Intel Atom. There are (more than) rumors that Samsung will use Atoms in some future tablet and possibly even smart phones. I guess they know what they are doing. We'll see.
I need to make a correction. The crunching time stabilized in the range of 10 - 11 hrs now; maybe some background tasks after the new installation have slowed down the system (virus check, defragmentation, update-check aso).
My atom is a D525 which is certainly not the one Samsung will choose for the new tablets. New devices have a lot of enhancements on board; my one is 45nm, L1 cache 24/32k, L2 512k, L3 0k.
AFAIK Apple has plans to use ARM devices for Laptops. It looks like we will see a future with a wide variety of cpu's and platforms. Will not make it easier for software developement!
I notice the Raspberry Pi app has updated to 1.06 now. Were there problems with 1.05 or some further improvements?
There was a small bug fix, and the new app was compiled with a different toolchain (cross compiled on an Intel x86 Linux host like the Android (and Windows) app versions). Before that, it was a bit cumbersome to build the app on the Raspberry Pi itself, and it didn't integrate well into our automated continuous integration solution (Jenkins).
I've attached my HTC One S to Albert@home, not had any validations yet, eithier the app gets a SIGSEGV: segmentation violation, or if it completes, it then gets a Validate error, running the Official Android 7.0.58 Boinc,
one thing to Note, my Android kernel is newer than anyone else's here, being Android 3.4.10-g8d7cd09, it has some new Power Save Options (which i have switched off, but i don't trust the kernel not to do other power save things unbided)
I was previously running NativeBoinc on the HTC One S, Both the Setiathome app and the PrimeGrid apps would also regularly get segmentation violations too,
the GridGrid app would sometimes get app error: 9, i think this is when android kills the app to free up memory, also often one of the PrimeGrid Wu's would error if:
a) the HTC switched over to battery power, b) If the Play Store downloaded and then updated any apps, it wasn't the downloading that caused the errors, more the updating,
earlier when i ran the older kernel (I think it was around 3.0.x), i'm sure i only got the app error: 9 condition,
RE: It still hasn't quite
)
Now its finished. 31 hours and 45 minutes. Link to wu is here
RE: RE: It still hasn't
)
Cool, validated against an Android (NEON) task that took a bit less than half as long to finish.
Cheers
HB
The rest of them have also
)
The rest of them have also knocked over one each (I have 5 Pi's on the job). They seem to be a consistent 31 hours and 35 to 40 minutes. Great job guys :-)
This long weekend I made some
)
This long weekend I made some tests for speed comparison.
My old, retired Intel Atom 2x1.8GHz has seen a new spring. A clean win7 with actual Boinc Manager and a project which is availanble for both platforms and validating against each other.
Pogs.
My Nexus runs these apps in ~8 hrs, using 2 of the 4 cores it finishes ~6 wu's within 24 hrs.
The Atom is running 4 threads, for 16 hrs now. The fastest wu has reached now 64%, the slowest 41%. Even my phone is faster.
My i3 3220 needs ~6000 sec's/wu running 4 threads.
I think ARM, Parelela & Co are the future. In terms of speed, power consumption, amount of devices available and headroom for improvements.
All it needs is some advertising for arm-projects. They can easily replace the older laptops and desktops.
And the Atom? I think, the spring will end soon ...
Hi! I think it's too early
)
Hi!
I think it's too early for funeral eulogies wrt. Intel Atom. There are (more than) rumors that Samsung will use Atoms in some future tablet and possibly even smart phones. I guess they know what they are doing. We'll see.
Cheers
HB
I need to make a correction.
)
I need to make a correction. The crunching time stabilized in the range of 10 - 11 hrs now; maybe some background tasks after the new installation have slowed down the system (virus check, defragmentation, update-check aso).
My atom is a D525 which is certainly not the one Samsung will choose for the new tablets. New devices have a lot of enhancements on board; my one is 45nm, L1 cache 24/32k, L2 512k, L3 0k.
AFAIK Apple has plans to use ARM devices for Laptops. It looks like we will see a future with a wide variety of cpu's and platforms. Will not make it easier for software developement!
I notice the Raspberry Pi app
)
I notice the Raspberry Pi app has updated to 1.06 now. Were there problems with 1.05 or some further improvements?
RE: I notice the Raspberry
)
There was a small bug fix, and the new app was compiled with a different toolchain (cross compiled on an Intel x86 Linux host like the Android (and Windows) app versions). Before that, it was a bit cumbersome to build the app on the Raspberry Pi itself, and it didn't integrate well into our automated continuous integration solution (Jenkins).
I expect no significant performance change.
Cheers
HB
RE: RE: I notice the
)
I'd say slightly faster, around 500 seconds approx from the small sample completed so far.
I've attached my HTC One S to
)
I've attached my HTC One S to Albert@home, not had any validations yet, eithier the app gets a SIGSEGV: segmentation violation, or if it completes, it then gets a Validate error, running the Official Android 7.0.58 Boinc,
one thing to Note, my Android kernel is newer than anyone else's here, being Android 3.4.10-g8d7cd09, it has some new Power Save Options (which i have switched off, but i don't trust the kernel not to do other power save things unbided)
Computer 7471
I was previously running NativeBoinc on the HTC One S, Both the Setiathome app and the PrimeGrid apps would also regularly get segmentation violations too,
the GridGrid app would sometimes get app error: 9, i think this is when android kills the app to free up memory, also often one of the PrimeGrid Wu's would error if:
a) the HTC switched over to battery power, b) If the Play Store downloaded and then updated any apps, it wasn't the downloading that caused the errors, more the updating,
earlier when i ran the older kernel (I think it was around 3.0.x), i'm sure i only got the app error: 9 condition,
Claggy