FAH on mobile devices [Android 4.4+ Only for now]
Moderators: Site Moderators, FAHC Science Team
-
- Posts: 96
- Joined: Wed Dec 05, 2007 7:15 am
- Hardware configuration: PS3, Phenom II X4, QX9775, HD 8570
- Contact:
Re: FAH on mobile devices [Not]
I like the idea of having a folding monitor app on smart phone or tablet. very nice.
Carnivorous Labs
http://garden-experiment.blogspot.com/
http://garden-experiment.blogspot.com/
Re: FAH on mobile devices [Not]
I would say this will become a GO soon, as Nvidia announced the Tegra K1 at the CES 2014 today ![Smile :)](./images/smilies/icon_smile.gif)
http://www.anandtech.com/show/7622/nvidia-tegra-k1
365 GFLOPS @ 5 Watts
I would say there are possibilities coming up.
It is more power then a PS3 or XBOX360 with only 1/20th of the power draw.
![Smile :)](./images/smilies/icon_smile.gif)
http://www.anandtech.com/show/7622/nvidia-tegra-k1
365 GFLOPS @ 5 Watts
![Smile :)](./images/smilies/icon_smile.gif)
It is more power then a PS3 or XBOX360 with only 1/20th of the power draw.
-
- Posts: 45
- Joined: Fri Jan 03, 2014 4:53 am
- Hardware configuration: A: i5 + 2 GTX 660
B: i5 + 2 GTX 670
C: i7 + GTX670
Re: FAH on mobile devices [Not]
I can be convinced, but I'll believe that when I see it.JS1982 wrote:I would say this will become a GO soon, as Nvidia announced the Tegra K1 at the CES 2014 today
http://www.anandtech.com/show/7622/nvidia-tegra-k1
365 GFLOPS @ 5 WattsI would say there are possibilities coming up.
It is more power then a PS3 or XBOX360 with only 1/20th of the power draw.
Jim
Good science and heat for my basement you say?
-
- Posts: 10189
- Joined: Thu Nov 29, 2007 4:30 pm
- Hardware configuration: Intel i7-4770K @ 4.5 GHz, 16 GB DDR3-2133 Corsair Vengence (black/red), EVGA GTX 760 @ 1200 MHz, on an Asus Maximus VI Hero MB (black/red), in a blacked out Antec P280 Tower, with a Xigmatek Night Hawk (black) HSF, Seasonic 760w Platinum (black case, sleeves, wires), 4 SilenX 120mm Case fans with silicon fan gaskets and silicon mounts (all black), a 512GB Samsung SSD (black), and a 2TB Black Western Digital HD (silver/black).
- Location: Arizona
- Contact:
Re: FAH on mobile devices [Not]
365 GFLOPS of pixel data means nothing to GFLOPS of folding data. Apples to Oranges.JS1982 wrote:I would say this will become a GO soon, as Nvidia announced the Tegra K1 at the CES 2014 today
http://www.anandtech.com/show/7622/nvidia-tegra-k1
365 GFLOPS @ 5 WattsI would say there are possibilities coming up.
It is more power then a PS3 or XBOX360 with only 1/20th of the power draw.
Go? Ya, maybe. No mention of OpenCL support, so no assurance to support core 17. Strike One? It does have 192 CUDA cores and 1 SMX, which is exactly half of one low powered 740M GPU, making K1 very low powered, computationally speaking. May not make the deadlines on core 15. Strike Two? That assumes that the now EndOfLife core 15 is still around by the time this comes to market, or else it may not fold. Strike Three?
How to provide enough information to get helpful support
Tell me and I forget. Teach me and I remember. Involve me and I learn.
Tell me and I forget. Teach me and I remember. Involve me and I learn.
-
- Posts: 10189
- Joined: Thu Nov 29, 2007 4:30 pm
- Hardware configuration: Intel i7-4770K @ 4.5 GHz, 16 GB DDR3-2133 Corsair Vengence (black/red), EVGA GTX 760 @ 1200 MHz, on an Asus Maximus VI Hero MB (black/red), in a blacked out Antec P280 Tower, with a Xigmatek Night Hawk (black) HSF, Seasonic 760w Platinum (black case, sleeves, wires), 4 SilenX 120mm Case fans with silicon fan gaskets and silicon mounts (all black), a 512GB Samsung SSD (black), and a 2TB Black Western Digital HD (silver/black).
- Location: Arizona
- Contact:
Re: FAH on mobile devices [Not]
Also makes you wonder why they compared the K1 to an old PS3 and an old XBox instead of the current gen of gaming consoles? ![Wink ;)](./images/smilies/icon_wink.gif)
![Wink ;)](./images/smilies/icon_wink.gif)
How to provide enough information to get helpful support
Tell me and I forget. Teach me and I remember. Involve me and I learn.
Tell me and I forget. Teach me and I remember. Involve me and I learn.
Re: FAH on mobile devices [Not]
I tried to be positive, but whipped of the table this way... Damn... But you know more tech details, so guess you're right...
And we need positivity so much right now. Look at the amount of active cpu's mentioned on the site (http://fah-web.stanford.edu/cgi-bin/mai ... e=osstats2)
This number is dropping with around 1 thousand every day for a while now... We need to go up, not down...
And we need positivity so much right now. Look at the amount of active cpu's mentioned on the site (http://fah-web.stanford.edu/cgi-bin/mai ... e=osstats2)
This number is dropping with around 1 thousand every day for a while now... We need to go up, not down...
-
- Posts: 10189
- Joined: Thu Nov 29, 2007 4:30 pm
- Hardware configuration: Intel i7-4770K @ 4.5 GHz, 16 GB DDR3-2133 Corsair Vengence (black/red), EVGA GTX 760 @ 1200 MHz, on an Asus Maximus VI Hero MB (black/red), in a blacked out Antec P280 Tower, with a Xigmatek Night Hawk (black) HSF, Seasonic 760w Platinum (black case, sleeves, wires), 4 SilenX 120mm Case fans with silicon fan gaskets and silicon mounts (all black), a 512GB Samsung SSD (black), and a 2TB Black Western Digital HD (silver/black).
- Location: Arizona
- Contact:
Re: FAH on mobile devices [Not]
I'll be glad when the core_17 stats numbers are fixed. Then we'll see if all the Chicken Littles about the falling skies, er, clients were correct or not. We'll see who eats the crow. ![Wink ;)](./images/smilies/icon_wink.gif)
BTW, ATI numbers tripled the last few days while the Core_17 server was offline and people had to fold Core_16 again. (250 active jumped to 750) Not the 2000+ it was earlier this year, but who knows...?
![Wink ;)](./images/smilies/icon_wink.gif)
BTW, ATI numbers tripled the last few days while the Core_17 server was offline and people had to fold Core_16 again. (250 active jumped to 750) Not the 2000+ it was earlier this year, but who knows...?
How to provide enough information to get helpful support
Tell me and I forget. Teach me and I remember. Involve me and I learn.
Tell me and I forget. Teach me and I remember. Involve me and I learn.
Re: FAH on mobile devices [Not]
Boinc already has a mobile app for android, Ive used it before. It also has this very handy option for people that are always on the go and not next to their charger. The option is simply to autostart the client when the phone is plugged in. I have a small collection of android devices, a dual core and two quad cores. the quad cores are always by a charger in my car or home or at the office. Personally, I would run FAH on my mobile devices almost 24/7 . Being that I used to be in the cell phone business (tech department of course ) I still have some contacts and could help promote an app like this in store fronts.7im wrote:I think mobile folding was dismissed at the appropriate speed. The power (processing wise) and the power (battery life) is not conducive to folding.
If at some time in the future this changes, they will certainly revisit this option. Until then, consider it a no go, and a dead topic.
There are many things about x86 and ARM that are different. ARM has some real advantages in the way it processes data. ARM should not be dismissed as a possible folding platform. A lot of phones that are coming out today and the processor in my nexus 7 tablet and GS3 can probably outperform some cpus people are folding on today. Oh, the boinc app even has the ability to use the phones built in gpu.... UK has already released an eight core ARM phone, i think its the Note 3 UK version.
Its been a while since Ive paid attention to the ARM inner workings but I do know they have advantages that if used properly could be used for certain tasks very efficiently.
Porting to ARM should not be hard to do with android since its linux based. Makes me wish I had the extra time to look into this, I dare say with enough time I could port the command line linux FAH client into ARM. Im sure there would be some dependencies that would have to be recompiled to ARM as well before compiling the final ARM client. If anyone wants to tackle this Ill be standing by with what android knowledge I still remember from being a cell phone tech.
When I ran Boinc on my phone the heat level was not very bad either...
Another very big part to consider, is that as of Oct 2013 there were over 40 million GS4 phones sold ( high speed quad core ARMs with Im quite sure what is an Nvidia based gpu). And that is only the GS4 up to last october, and it continues to sell like hotcakes. The power of the mobile network is nothing to be under estimated.
----- EDIT - my battery held up pretty good even when not on the charger using the boinc app
-
- Posts: 10189
- Joined: Thu Nov 29, 2007 4:30 pm
- Hardware configuration: Intel i7-4770K @ 4.5 GHz, 16 GB DDR3-2133 Corsair Vengence (black/red), EVGA GTX 760 @ 1200 MHz, on an Asus Maximus VI Hero MB (black/red), in a blacked out Antec P280 Tower, with a Xigmatek Night Hawk (black) HSF, Seasonic 760w Platinum (black case, sleeves, wires), 4 SilenX 120mm Case fans with silicon fan gaskets and silicon mounts (all black), a 512GB Samsung SSD (black), and a 2TB Black Western Digital HD (silver/black).
- Location: Arizona
- Contact:
Re: FAH on mobile devices [Not]
Please read back through this thread or the six others just like it that already explains why arm does not work for fah.
And the BOINC client on a phone is a gimmick. It doesn't do much science at all.
And the BOINC client on a phone is a gimmick. It doesn't do much science at all.
How to provide enough information to get helpful support
Tell me and I forget. Teach me and I remember. Involve me and I learn.
Tell me and I forget. Teach me and I remember. Involve me and I learn.
Re: FAH on mobile devices [Not]
I have reviewed the thread, I must first point out most of these posts up until the last page are from 2010-2011, rather outdated. The post about the seti app is actually incorrect from its current state. It may have been like that years ago but its now utilizes even the built in GPU on high end phones. ( correct me if im wrong there but when i tried that app not long ago it seemed pretty advanced, not like what I read reported here)
Also, the post about phones /ARMs being measured in mflops is very outdated. The current standard for for good arm phone GPU's is something like the ARM Mali-T628 600 MHz \ per shader and clocks in at 115.2 GFLOPS. This is already being out done by the Mali t760 and other chips that put out roughly 330 Gflops. Most phones also come with 2-3 gigs of ram now as well. One must also consider there are about 1.5 billion smart phone users that upgrade their phones every few years.
Just my two cents, I think the original poster had an idea that now holds ground, or certainly will in the future as these devices continue to overpower the old standards of x86 and mobile GPUs / CPU's. Im going to make a prediction and say, some day down the line this app will eventually exist. Maybe it will take years, but I don't think ARM is going to slow down progress with the high demand for fast mobile devices. There are opencl bench tests you can download and try on your phone.
Also, the post about phones /ARMs being measured in mflops is very outdated. The current standard for for good arm phone GPU's is something like the ARM Mali-T628 600 MHz \ per shader and clocks in at 115.2 GFLOPS. This is already being out done by the Mali t760 and other chips that put out roughly 330 Gflops. Most phones also come with 2-3 gigs of ram now as well. One must also consider there are about 1.5 billion smart phone users that upgrade their phones every few years.
Just my two cents, I think the original poster had an idea that now holds ground, or certainly will in the future as these devices continue to overpower the old standards of x86 and mobile GPUs / CPU's. Im going to make a prediction and say, some day down the line this app will eventually exist. Maybe it will take years, but I don't think ARM is going to slow down progress with the high demand for fast mobile devices. There are opencl bench tests you can download and try on your phone.
Re: FAH on mobile devices [Not]
FACT: There a lot of mobile devices out there.
FACT: The speed with which current technology hardware can compute increases with each new hardware generation.
FACT: The power needed to perform a fixed set of computations decreases with each new hardware generation.
FACT: Battery power is a significant limitation to what mobile devices can do.
There is an important distinction between integer computation and floating point computation and realistically, they're done by different hardware components. In the early days of desktop computing, the 8086 had an optional "math coprocessor called the 8087 which lot of computers never needed. That trend continued beyond the 80386 + 80387 and it wasn't until the Pentium was developed that both functions were integrated onto a single piece of silicon. Mobile hardware has been going through a similar evolutionary path although most floating point operations have migrated from the CPU to the GPU.
Why is this important? Two reasons: Because the hardware designer has to make tradeoffs and (s)he can allocate more or less area to the floating vs integer. Because some DC projects are based mainly on integer operations and others are based mainly on floating point operations. (For FAH, float speed is critical.)
The idea of only using power when the device is on the charger is probably a good idea since having a dead battery on your phone certainly limits its usefulness (and that option is already part of the standard FAH client for laptops).
I think it's reasonable to assume that the potential contribution to DC projects (including FAH) by mobile devices will eventually reach some critical level but will absolutely refrain from predicting when that might happen, particularly for a project like FAH because of its need for continuous high levels of computation compared to the low computational capabilities of mobile hardware. (It's a lot like a parent trying to answer the kids' question "are we there yet?" except we've never driven this way before and we don't have a GPS that can predict it for us.)
FACT: The speed with which current technology hardware can compute increases with each new hardware generation.
FACT: The power needed to perform a fixed set of computations decreases with each new hardware generation.
FACT: Battery power is a significant limitation to what mobile devices can do.
There is an important distinction between integer computation and floating point computation and realistically, they're done by different hardware components. In the early days of desktop computing, the 8086 had an optional "math coprocessor called the 8087 which lot of computers never needed. That trend continued beyond the 80386 + 80387 and it wasn't until the Pentium was developed that both functions were integrated onto a single piece of silicon. Mobile hardware has been going through a similar evolutionary path although most floating point operations have migrated from the CPU to the GPU.
Why is this important? Two reasons: Because the hardware designer has to make tradeoffs and (s)he can allocate more or less area to the floating vs integer. Because some DC projects are based mainly on integer operations and others are based mainly on floating point operations. (For FAH, float speed is critical.)
The idea of only using power when the device is on the charger is probably a good idea since having a dead battery on your phone certainly limits its usefulness (and that option is already part of the standard FAH client for laptops).
I think it's reasonable to assume that the potential contribution to DC projects (including FAH) by mobile devices will eventually reach some critical level but will absolutely refrain from predicting when that might happen, particularly for a project like FAH because of its need for continuous high levels of computation compared to the low computational capabilities of mobile hardware. (It's a lot like a parent trying to answer the kids' question "are we there yet?" except we've never driven this way before and we don't have a GPS that can predict it for us.)
Posting FAH's log:
How to provide enough info to get helpful support.
How to provide enough info to get helpful support.
-
- Posts: 10189
- Joined: Thu Nov 29, 2007 4:30 pm
- Hardware configuration: Intel i7-4770K @ 4.5 GHz, 16 GB DDR3-2133 Corsair Vengence (black/red), EVGA GTX 760 @ 1200 MHz, on an Asus Maximus VI Hero MB (black/red), in a blacked out Antec P280 Tower, with a Xigmatek Night Hawk (black) HSF, Seasonic 760w Platinum (black case, sleeves, wires), 4 SilenX 120mm Case fans with silicon fan gaskets and silicon mounts (all black), a 512GB Samsung SSD (black), and a 2TB Black Western Digital HD (silver/black).
- Location: Arizona
- Contact:
Re: FAH on mobile devices [Not]
CygnusXI, not all GFLOPS are created equal. Please specify how those are measured and where quoted from so we can update ourselves... Integer Ops means nothing to FAH. Floating Point Ops means everything.
How to provide enough information to get helpful support
Tell me and I forget. Teach me and I remember. Involve me and I learn.
Tell me and I forget. Teach me and I remember. Involve me and I learn.
-
- Posts: 95
- Joined: Wed Dec 05, 2007 10:23 pm
- Hardware configuration: Apple Mac Pro 1,1 2x2.66 GHz Dual-Core Xeon w/10 GB RAM | EVGA GTX 960, Zotac GTX 750 Ti | Ubuntu 14.04 LTS
Dell Precision T7400 2x3.0 GHz Quad-Core Xeon w/16 GB RAM | Zotac GTX 970 | Ubuntu 14.04 LTS
Apple iMac Retina 5K 4.00 GHz Core i7 w/8 GB RAM | OS X 10.11.3 (El Capitan) - Location: Michiana, USA
Re: FAH on mobile devices [Not]
It's baa-ack! From Sony's announcement from last week's International CES®:
http://blogs.sonymobile.com/2015/01/12/ ... s-disease/
http://blogs.sonymobile.com/2015/01/12/ ... s-disease/
-
- Posts: 57
- Joined: Fri Dec 28, 2007 9:07 am
- Hardware configuration: Computer 1:
CPU: Intel Q6600@2,4GHz
RAM: 8GB
OS: Windows 7 SP1
Video: EVGA GTX550Ti SC (NVIDIA GeForce GTX550Ti GPU - 1GB GDDR5)
(OC: GPU@981MHz / Shaders@1962 / Memory@4514)
PSU: OCZ StealthXtream 600 Watt
Client 7.4.4
Computer 2:
CPU: AMD AthlonII X4 635 @2.9GHz
RAM: 4GB
OS: Windows Server 2008 R2 SP2
Client 7.4.4, configured as a service
Computer 3:
CPU: Intel Core i7-4790K @4.0GHz
GPU: EVGA GTX980 @1.518GHz
RAM: 32 GB
OS: Windows 7 SP1
Client 7.4.4
Computer 4:
CPU: Intel Core i5 M560 @2,67GHz
RAM: 4 GB
OS: Windows 7 Enterprise
Client: Win-SMP2
Computer 5:
CPU: Intel Core i3 4370 @3.8GHz
RAM: 8GB
OS: Windows 7 SP1
Client 7.4.4 configured as a service - Location: Netherlands
Re: FAH on mobile devices [Not]
Could anyone update the title of this thread by removing the '[Not]':
https://folding.stanford.edu/home/new-i ... n-android/
TIA,
Corné
https://folding.stanford.edu/home/new-i ... n-android/
TIA,
Corné
-
- Posts: 10189
- Joined: Thu Nov 29, 2007 4:30 pm
- Hardware configuration: Intel i7-4770K @ 4.5 GHz, 16 GB DDR3-2133 Corsair Vengence (black/red), EVGA GTX 760 @ 1200 MHz, on an Asus Maximus VI Hero MB (black/red), in a blacked out Antec P280 Tower, with a Xigmatek Night Hawk (black) HSF, Seasonic 760w Platinum (black case, sleeves, wires), 4 SilenX 120mm Case fans with silicon fan gaskets and silicon mounts (all black), a 512GB Samsung SSD (black), and a 2TB Black Western Digital HD (silver/black).
- Location: Arizona
- Contact:
Re: FAH on mobile devices [Not]
[Not] to [Sony Only]? ![Wink ;)](./images/smilies/icon_wink.gif)
![Wink ;)](./images/smilies/icon_wink.gif)
How to provide enough information to get helpful support
Tell me and I forget. Teach me and I remember. Involve me and I learn.
Tell me and I forget. Teach me and I remember. Involve me and I learn.