Hi there! This is my first post and I'd like to share a dream of me with you, looking for discussion and hoping to learn lots of things. Let me say beforehand that I'm unexperienced with hardware and that everything I write here is information I collected by surfing and asking people. Many of the things I write are probably illusions and utopias and I hope to get confronted with reality(TM) in this thread.
My idea is to build a computer that scales with its usage. This means that it consists of a fast, high-power computation part (containing main CPU, GPU) and a low-power headless storage part (containing a small CPU and a few SSDs with RAID). The fast part only gets turned on when needed, so the construct can awake to a monster when required, but otherwise has low power consumption when mostly idle (still able to perform basic NAS-style tasks, e.g. non-converting DLNA server, playing back a movie, synching some data at low rate). This idea being very general, I try to be as open as possible about what a possible implementation could look like. I'd like to consider high-cost and non-conventional solutions as well, dreaming in all kinds of directions and either end up with the super-cool PC of my dreams or having at least learned lots of things.
I've head a few design ideas which I would like to present to you (feel free to destroy them but please tell me why they're irrealistic):
Idea 1: Big and Small, both self-made and Small contains the data: A big self-made case that contains two computers. The small one really is a NAS. The power consumption could be pushed down to 10W if I use Xeon D (so I heared), while still being RAID-capable. The big computer (in the same case) is the beast and can be booted (e.g. wake-on-LAN) by the NAS. Both machines are connected by a smokin' fast kind of network (maybe SFP?) and the big computer only has a system disk (user files reside on the network mounted NAS). An Arduino controlled by the NAS could even physically unplug the power supply of the big machine when it's not running in order to save power. Problems: I heared that it's hard / super expensive to get hardware that provides decent RAID support while consuming 10W only. Also it's unclear which protocol to use to mount the home partition in order to achieve minimal latency and maximal throughput.
Idea 2: Big and Small, Small is commercial and contains the data: A commercial NAS (meaning: one that I don't build myself) and a fast computer. Again, the NAS gets mounted by the computer upon boot. Problems: I've seen a few commercial NAS and none has ever made me happy. The software running on them is out-dated or even locked, and even if I manage to install some fresh Linux, the architecture is often so exotic that not all of my software runs on it. And most importantly: I've never seen a NAS that's fast enough to replace a SATA-connected SSD.
Idea 3: Big and Small, both self-made, shared external storage: Some kind of shared storage that is not a NAS and that gets shared by a big machine (the beast) and a low-end machine such as Raspberry Pi. The problem here: I have never heared of any kind of fast shared storage (with consistent simultaneous access) that is not a NAS.
Idea 4: Big and Small, both self-made, each contains part of the data: This is the capitulation plan and would probably be the classic solution: "hot" data (data I currently work on) sits on the big computer. The NAS takes the role of an archive. Problems: Need to decide what data goes where, cannot utilize storage on one computer for the other (too slow), lots of waiting for data to sync between computers, need to run the big machine to access data that hasn't gone to the NAS yet.
I'm looking forward to this discussion and I hope some of you like to dream with me. I'm also happy to get links to further reading.
My idea is to build a computer that scales with its usage. This means that it consists of a fast, high-power computation part (containing main CPU, GPU) and a low-power headless storage part (containing a small CPU and a few SSDs with RAID). The fast part only gets turned on when needed, so the construct can awake to a monster when required, but otherwise has low power consumption when mostly idle (still able to perform basic NAS-style tasks, e.g. non-converting DLNA server, playing back a movie, synching some data at low rate). This idea being very general, I try to be as open as possible about what a possible implementation could look like. I'd like to consider high-cost and non-conventional solutions as well, dreaming in all kinds of directions and either end up with the super-cool PC of my dreams or having at least learned lots of things.
I've head a few design ideas which I would like to present to you (feel free to destroy them but please tell me why they're irrealistic):
Idea 1: Big and Small, both self-made and Small contains the data: A big self-made case that contains two computers. The small one really is a NAS. The power consumption could be pushed down to 10W if I use Xeon D (so I heared), while still being RAID-capable. The big computer (in the same case) is the beast and can be booted (e.g. wake-on-LAN) by the NAS. Both machines are connected by a smokin' fast kind of network (maybe SFP?) and the big computer only has a system disk (user files reside on the network mounted NAS). An Arduino controlled by the NAS could even physically unplug the power supply of the big machine when it's not running in order to save power. Problems: I heared that it's hard / super expensive to get hardware that provides decent RAID support while consuming 10W only. Also it's unclear which protocol to use to mount the home partition in order to achieve minimal latency and maximal throughput.
Idea 2: Big and Small, Small is commercial and contains the data: A commercial NAS (meaning: one that I don't build myself) and a fast computer. Again, the NAS gets mounted by the computer upon boot. Problems: I've seen a few commercial NAS and none has ever made me happy. The software running on them is out-dated or even locked, and even if I manage to install some fresh Linux, the architecture is often so exotic that not all of my software runs on it. And most importantly: I've never seen a NAS that's fast enough to replace a SATA-connected SSD.
Idea 3: Big and Small, both self-made, shared external storage: Some kind of shared storage that is not a NAS and that gets shared by a big machine (the beast) and a low-end machine such as Raspberry Pi. The problem here: I have never heared of any kind of fast shared storage (with consistent simultaneous access) that is not a NAS.
Idea 4: Big and Small, both self-made, each contains part of the data: This is the capitulation plan and would probably be the classic solution: "hot" data (data I currently work on) sits on the big computer. The NAS takes the role of an archive. Problems: Need to decide what data goes where, cannot utilize storage on one computer for the other (too slow), lots of waiting for data to sync between computers, need to run the big machine to access data that hasn't gone to the NAS yet.
I'm looking forward to this discussion and I hope some of you like to dream with me. I'm also happy to get links to further reading.