WARNING: This website is obsolete! Please follow this link to get to the new Albert@Home website!

Posts by Patrick

1) Message boards : Problems and Bug Reports : BRP4U (Raspberry Pi , single DM tasks) feedback thread (Message 112488)
Posted 2 May 2013 by Patrick
Post:
Ok thank you

I´ve buyed me an S3 before yesterday but not for crunching it´s such a great fast Smartphone.
But everyone has to decide this by himself.
I wish you many fast mobile devices if the project is released to Einstein.
You all are doing good work.
2) Message boards : Problems and Bug Reports : BRP4U (Raspberry Pi , single DM tasks) feedback thread (Message 112479)
Posted 30 Apr 2013 by Patrick
Post:
First Valid result on my Galaxy S 1 mini with app 1.03(VFP)

http://albert.phys.uwm.edu/results.php?hostid=6955&offset=0&show_names=0&state=3&appid=

long runtime but valid :)
3) Message boards : Problems and Bug Reports : BRP4U (Raspberry Pi , single DM tasks) feedback thread (Message 112478)
Posted 30 Apr 2013 by Patrick
Post:
That´s the funniest cooling solution i´ve ever seen. :)

But for those who haven´t so a small fan at home be warned...

Don´t forget your Smartphone in the Refrigerator if you go to work! :)
4) Message boards : Problems and Bug Reports : BRP4U (Raspberry Pi , single DM tasks) feedback thread (Message 112460)
Posted 24 Apr 2013 by Patrick
Post:
Ok thanks for that info
I think then it´s not especially good for live crunching but for testing it´s ok.
I´ve send you my log of nativeboinc to MPI... i thought there´s something wrong with my device or firmware :)
delete it whatever
5) Message boards : Problems and Bug Reports : BRP4U (Raspberry Pi , single DM tasks) feedback thread (Message 112458)
Posted 24 Apr 2013 by Patrick
Post:
That´s my Scheduler log here from albert if that helps
2013-04-24 13:40:52.0424 [PID=9073] Request: [USER#xxxxx] [HOST#6955] [IP xxx.xxx.xxx.58] client 7.0.36
2013-04-24 13:40:52.0435 [PID=9073 ] [send] Not using matchmaker scheduling; Not using EDF sim
2013-04-24 13:40:52.0436 [PID=9073 ] [send] CPU: req 0.00 sec, 0.00 instances; est delay 0.00
2013-04-24 13:40:52.0436 [PID=9073 ] [send] work_req_seconds: 0.00 secs
2013-04-24 13:40:52.0436 [PID=9073 ] [send] available disk 3.60 GB, work_buf_min 8640
2013-04-24 13:40:52.0436 [PID=9073 ] [send] active_frac 0.997705 on_frac 0.928794
2013-04-24 13:40:52.0436 [PID=9073 ] [send] p_vm_extensions_disabled: no
2013-04-24 13:40:52.0436 [PID=9073 ] [send] CPU features: swp half thumb fastmult vfp edsp java
2013-04-24 13:40:52.4394 [PID=9073 ] Sending reply to [HOST#6955]: 0 results, delay req 60.00
2013-04-24 13:40:52.4397 [PID=9073 ] Scheduler ran 0.403 seconds
6) Message boards : Problems and Bug Reports : BRP4U (Raspberry Pi , single DM tasks) feedback thread (Message 112457)
Posted 24 Apr 2013 by Patrick
Post:
i didn´t rooted my device or something like that and the firmware cames from the manufacturer.
That´s all i can say.
7) Message boards : Problems and Bug Reports : BRP4U (Raspberry Pi , single DM tasks) feedback thread (Message 112456)
Posted 24 Apr 2013 by Patrick
Post:
My device runs on armv6-compatible processor rev 5(v6l)@600mhz
processor features are swp half thumb fastmult vfp edsp java
OS: Adroid: 2.6.35.7-perf-CL1178095
no usual gpu´s found
last firmware update(FOTA firmware over the air) i did was for a week or two
I´m running following task

p2030.20120226.G194.26-02.01.S.b6s0g0.00000-792-4
using einsteinbinary_BRP4U version 103 (VFP) in slot 0

Yes it runs brp single dm 1.03 but it looks like it´s how you said with neon doubled as fast as with 1.02 sorry that i aborted the 1.02 so you have no comparison
now after 9:48:06 it has crunched 11,273 percentage of the task isn´t that good for this machine?

8) Message boards : Problems and Bug Reports : BRP4U (Raspberry Pi , single DM tasks) feedback thread (Message 112455)
Posted 24 Apr 2013 by Patrick
Post:
I played around with those settings for the Raspi compile but didn't see any significant performance increase so far.

You know playing around with settings (like i did too with my phone temperature settings)is not the best solution but sometimes it can help :D
I didn´t want to encourage you with that. :)
9) Message boards : Problems and Bug Reports : BRP4U (Raspberry Pi , single DM tasks) feedback thread (Message 112452)
Posted 24 Apr 2013 by Patrick
Post:
That looks like 5 times faster then my armv6 device @600mhz and your has 1300
both with app 1.03 not bad this v7.
Your device is a dualcore.
I don´t know if there are existing armv6 with multicore.
Ok if i watch after the Samsung Galaxy mini 2 for example it is to have for 99 Euro and uses an armv7 @800mhz so my estimation over the sell price was wrong.
I went out from prices of actual popular phones like nexus4 s3 or note2
I´m not disappointed if the v6 support for NEON will be dropped.
10) Message boards : Problems and Bug Reports : BRP4U (Raspberry Pi , single DM tasks) feedback thread (Message 112449)
Posted 24 Apr 2013 by Patrick
Post:
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.



11) Message boards : Problems and Bug Reports : BRP4U (Raspberry Pi , single DM tasks) feedback thread (Message 112448)
Posted 24 Apr 2013 by Patrick
Post:
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.
12) Message boards : Problems and Bug Reports : BRP4U (Raspberry Pi , single DM tasks) feedback thread (Message 112447)
Posted 24 Apr 2013 by Patrick
Post:
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.
13) Message boards : Problems and Bug Reports : BRP4U (Raspberry Pi , single DM tasks) feedback thread (Message 112438)
Posted 22 Apr 2013 by Patrick
Post:
Ok thanks now i´ve understood that.
To the point with battery overheating, if i go on local computing settings under client management i can choose at what for a temperature the client should do a break and i think that works good at the moment.
Just play around with that value and the task should be paused.
I had a buggy wifi connection so i have set the value "Use max % Processors" to 70%
that fixed it.
The other setting "Use max % cpu time" seems to be buggy in native boinc if i turn
that down a little bit the task starts and stops again and again.But i don´t know for sure if that´s a problem of the task or the nativeboinc program.
14) Message boards : Problems and Bug Reports : BRP4U (Raspberry Pi , single DM tasks) feedback thread (Message 112436)
Posted 22 Apr 2013 by Patrick
Post:
Thank you for that information and i wish you the best in developing and testing that the application can go up to the live servers.
If you watch here it looks like the arm v6 does not support NEON.
But however the arm v6 mobile phones are older models and as of arm v7 (Cortex A Series) supports it.

http://www.arm.com/products/processors/technologies/neon.php

http://www.arm.com/products/processors/instruction-set-architectures/index.php
15) Message boards : Problems and Bug Reports : BRP4U (Raspberry Pi , single DM tasks) feedback thread (Message 112434)
Posted 22 Apr 2013 by Patrick
Post:
I´ve downloaded the application 1.02 with native boinc 7.0.36 on a GT-S5570 with Android 2.3.6.
I had to enable "Run CPU versions of applications for which GPU versions are available" it has no gpu but it´s running.
Hopefully it gives a valid result in a week.
It has a Measured floating point speed of 50,44 million ops/sec and a Measured integer speed of 506.59 million ops/sec.
CPU specification is ARMv6-compatible processor rev 5 (v6l) @600MHz.

Good work.
16) Message boards : Problems and Bug Reports : FGRP application v 1.05 (OPENCL) feedback thread (Message 112428)
Posted 19 Apr 2013 by Patrick
Post:
The application produces with 1 cpu core and 1 gpu a little bit more computation output for FGRP as if i would run it on all of my 6 cores on the fx6100@3600Mhz
and that on a gpu fluctuation on my gtx 660 OC @1150Mhz at around 30%.
It looks like i could run 2 or 3 simultaneously if i would.
Yes i know actually for testing it´s not allowed.

Specifically 2 cpu cores and 0,5 gpu or 3 cpu cores 0,33 gpu.
But with 2GB of gpu memory it´s certainly possible?
17) Message boards : Problems and Bug Reports : FGRP application v 1.05 (OPENCL) feedback thread (Message 112385)
Posted 20 Mar 2013 by Patrick
Post:
No I´ve 2 valid results for FGRP opencl nvidia but one question.
Is the GTX 580 faster with that task(doubled so fast)as my GTX 660 because of higher DP Performance or what´s the difference there?
Yes of course i know different Hardware and OS can affect that too but doubled speed is a little bit hard for that differences i would say.

watch here

http://albert.phys.uwm.edu/workunit.php?wuid=268614

18) Message boards : Problems and Bug Reports : FGRP application v 1.05 (OPENCL) feedback thread (Message 112382)
Posted 20 Mar 2013 by Patrick
Post:
The first thing i found out with the FGRP Opencl for Nvidia is that i have 6 cpu cores 2 are normally free for the mainproject (2 BRP4 tasks simoultaneousy)and this FGRP opencl pushed the normally work on side even though that 2 cores are free.i don´t know if you doing this only here on albert or if that´s not correct.

To the runtime the task needed 1700 seconds on my system but the GPU load fluctuation jumped all the time up and down between 35percentage and zero.
At 40% of task completion the gpu did nothing for around 15seconds then it worked
again until to 95% it did again nothing for 87 seconds then it was uploaded and next task begun.I have to wait for validation now.






This material is based upon work supported by the National Science Foundation (NSF) under Grant PHY-0555655 and by the Max Planck Gesellschaft (MPG). Any opinions, findings, and conclusions or recommendations expressed in this material are those of the investigators and do not necessarily reflect the views of the NSF or the MPG.

Copyright © 2024 Bruce Allen for the LIGO Scientific Collaboration