Linked by Thom Holwerda on Mon 14th Mar 2011 23:05 UTC, submitted by sawboss
Permalink for comment 466335
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/21/13 21:38 UTC
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
Linked by Thom Holwerda on 04/18/13 11:21 UTC
More Features »
Sponsored Links



Member since:
2007-04-06
Well, I guess that would depend on the throughput of the whole system. If 480 ARM processors are only as fast as a handful of x86 cores, your memory bandwidth should prove no more a bottleneck. The article is sadly lacking on details such as clock speed, etc.
The nice thing about it is that it would offer a great deal of flexibility depending on how parallelizable your code is. Nobody's claiming you have to use all 480 cores at the same time; you could turn off half or more of them if that's all you can use, if your memory bus proves inadequate for your current task.