|
As with so many aspects of IT, there's no simple answer as "it depends" on the use case. Let me draw an analogy using vehicles:
Which is "best" (or "most powerful" if you like) - a sports car with a 400HP engine or tipper truck with a 600HP engine..? Of course, technically, if one focuses only on the engine output, then the truck is "best." However, if I wanted to win a race at my local motor racing circuit, I'd be much more likely in he sports car than the wagon. And vice-versa, if I've for 100 tonne of wheat to shift to market, the the sports car is almost useless and it's the truck I need.
So, for example, serving files is a pretty low CPU low & RAM activity, especially in a SOHO use case, so pretty much anything will do. My microserver has 16GB of RAM and barely uses 1GB (actually about 700MB) "just" serving files, but spin up a few virtual machines and it chomps through RAM really quickly. Whereas, real time transcoding or gaming will take as much CPU horsepower as you can give it (what happens with transcoding is picture quality and stream size is traded off against the available CPU horsepower.)
For basic SOHO file serving, I suspect either will be fine (though I'd be concerned about the NIC on the Pi - I'd prefer Gigabit - and I'd want to run Linux on it rather than Windows with 4GB.) SSD is of course silent in operation, though it's an expensive way to facilitate "seldom accessed" mass storage. |
|