Earlier quoted context omitted.
We are expecting the price to be cheaper than the V1, but the final price will be announced later this year.
Excuse me, whats the price of V1? Cant find it on your website.
V1 is $189
Show HN: Turing Pi 2 – a compact ARM cluster with 32 GB RAM
71–74 of 74 posts
Re: Show HN: Turing Pi 2 – a compact ARM cluster with 32 GB RAM
#72Brings to mind the Slashdot-era refrain "Imagine a Beowulf cluster of these!"
Re: Show HN: Turing Pi 2 – a compact ARM cluster with 32 GB RAM
#73Stupid question, how do these 4 SoCs share the 2x SATA ports? Do you assign them to a specific processor somehow? Are the other machines booting off of PXE boot?
The blog post[0] answers that: peripherals spread between nodes. [0] https://turingpi.com/turing-pi-2-announcement/
But like, how? Mounting a volume in read/write mode on more than one machine is obviously going to corrupt it
Re: Show HN: Turing Pi 2 – a compact ARM cluster with 32 GB RAM
#74Earlier quoted context omitted.
>>Besides academic uses to perhaps teach distributed systems on these are there any real world use cases for these clusters? A considerable amount of people is already assembling and running clusters of raspberry pis, including hosting companies. A cursory search through eBay or Amazon can provide you with an idea of how many people are already operating these small clusters and spending money on this sort of setup.…
I know people are building these the questions is for what, CI/CD for ARM like others mentioned is plausible but only if you are targeting the Pi or something very similar just due to how “fragmented” the ARM ecosystem is with its multiple uArchs. If you are building for mobile then it doesn’t makes sense to run CI/CD on the Pi and if you are targeting your own bespoke edge then likely having dev boards which can rep…
> I know people are building these the questions is for what, CI/CD for ARM like others mentioned is plausible but only if you are targeting the Pi or something very similar just due to how “fragmented” the ARM ecosystem is with its multiple uArchs.
I don't understand what point you tried to make. These hosting services, and also clients, are quite intentionally targetting the raspberry pi. More specifically, they do target Debian running on Raspberry Pi. I don't understand the confusion. I mean, is it also hard to understand why AWS users pay for ARM instances running Amazon's custom linux distro? In both the Pi and Graviton you can run nginx, nodejs, Python, ssh... So, what's the problem again?