Quoting yogesh powar (2016-09-20 20:39:31)
> I think RPis are famous but Debian has not endorsed it.
> Mainly because it requires Requires non-free blob [ref:
> Apart from price another good point about RPi3 is it comes with WiFi
> on board.
It would still help tremendously if you could elaborate on what your
actual use case for such a device is.
Unlike much personal hacking, school use often involve many concurrent
users, which means it is more likely reach bottlenecks.
Serving web content likely needs low latency and fast network...
RPi2/RPi3 has a particularly bad ethernet performance due to using one
chip for both ethernet and USB:
21/network-monitoring-with- iperf-raspberry-pi-vs-odroid- vs-banana-pi-vs-utilite/
RPi3 has builtin wifi but of notably low quality so comparable to
cheapest dongles (crazypi.com has a 7$ dongle):
01/iperf-wifi-comparison-on- raspberry-pi-raspberry-pi-3- vs-asus-vs-hawking-vs-linksys- vs-tp-link/
Running a file server (NAS) likely need fast disk access.
RPi2/RPi3 does not have SATA, only USB (which is shared with ethernet,
so every read or write to disk steals attention from network access).
Running applications likely need lots of memory (especially if disk is
slow so swapping is extra painful).
RPi2/RPi3 has 1GB DDR2 memory.
Power outages are common in India. RPi awkwardly draws more power than
a regular USB power supply, and require addon board to handle battery
I recommend OLinuXino LIME2 for such uses. At a price tag slightly above
RPi3, it has 1Gbit native ethernet, SATA, 1GB DDR3 memory, and natively
supports LiPo battery. Raw computing power is slower, but also does not
overheat as easily (adding a fan means a moving part easier breaking).
Only benefit I see in RPi is its name. It is popular but no good.
...but for _tinkering_ use - the original aim of the RPi project - maybe
none of those qualities matter, and you can save a few bucks and be hip.
* Jonas Smedegaard - idealist & Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/
[x] quote me freely [ ] ask before reusing [ ] keep private