> After the expansion completes, old blocks remain with their old data-to-parity ratio (e.g. 5-wide RAIDZ2, has 3 data to 2 parity), but distributed among the larger set of disks. New blocks will be written with the new data-to-parity
I live in South Africa. Myself and all my friends are sitting on around 100 Mbps up/down uncapped unshaped, no fair use policy each at around $100 USD monthly. A few of my friends are on Gigabit down, 200 up.
How is America behind on this? Everything is hosted there and cached there. Is it big business lobbying politicians to prevent them from having to compete? In South Africa we have dozens on ISPs and as an economy we're probably not far off from one US state. The competition has been great for consumers.
Yeah I wonder if in the future we won't see this as a terrible crime (pushing the next dopamine hit to a bunch of addicts) or if humanity needs to evolve to gain much much more self control.
Do you plan on having s Kubernetes storage provider? I like the idea of present a POSIX like mount to s container while paying per use for storage in S3
It's also relavant because there is a huge debate in defence community right now.
On the one hand you have many saying that the aircraft carrier might go the way if the battleship - more and more redundant in a world with landbase anti ship missile systems.
On the other hand there are some saying that ships will envolve to meet the threat.
My first cluster was Raspis and ODroids. The two issues I had - not everything runs on Arm (yet) and memory constraints were tough to work with.
My second cluster - 4 Atomic Pis. The (Intel Atom) quad cores were fine but the 2GB of memory was a real problem when I started playing with more interesting workloads.
The current "production" home cluster is 4 old laptops. They're earlier gen i7s and I've dropped 16GB of memory and 1TB spinning disks in each one. I've never been happier with a cluster. I've been free to spin whatever I want up and it just works. Using RKE to setup Kubernetes takes about 5 minutes to build a cluster and I'm using Longhorn for replicated container native storage. I've run experiments for work and my own experience. Whether its Redis / Cassandra cluster or a Kubernetes Operator I wrote, it can always handle it.
I had a cluster of ODroid C2s. It was nice - quad core, 2GB memory. But honestly, only for some workloads.
In my experience memory is a much bigger bottleneck than CPU, net IO or disk iops.
At the moment my favorite home lab cluster is a bunch of old laptops. They're quad cores too but I've dropped 16 GB of memory in each. It's doing a lot better. Right now the cluster is using 21GB of memory.
I'm able to run everything I've wanted as well as the occasional experiment to try something out.
If I could leave you with something - get more memory than you think you will need. That's been my experience anyway.
I use chisel for dancing across firewalls and across Big Corp's (TM) network policies. Chisel is fantastic. It wraps an SSH tunnel for proxying TCP (or reverse proxying) in HTTP, which I expose over TLS.
This advice might not be at all helpful, but anyway.
Consider checking the following:
- Number of CPUs. The number of CPUs is not CPU cores but Kubernetes millicores. 1 vCPU on CR = 400m (4/10 of a CPU core).
- Background processes - not recommended [https://stackoverflow.com/questions/61154349/google-cloud-ru...]
- Container size on disk. Google Cloud is fast. However they need to cap the moving container images around as they can't use all the network capacity for moving a 400MB Docker image. If you're not already, use multi-stage builds with tiny final images.
> There is emerging evidence to suggest that vitamin D deficiency is associated with adverse outcomes in COVID-19 patients. Conversely, vitamin D supplementation protects against an initial alveolar diffuse damage of COVID-19 becoming progressively worse.
When I played (at a national level) people would have a laptop connected and playing in another room. They would play the enemies moves on the computer as the player and playing in the tournament would play the moves made by the computer.
I remember a few people getting caught. What's funny about this is that the top players were still better than the AI running on a laptop (back then) and the cheaters occasionally got knocked out early on.
> After the expansion completes, old blocks remain with their old data-to-parity ratio (e.g. 5-wide RAIDZ2, has 3 data to 2 parity), but distributed among the larger set of disks. New blocks will be written with the new data-to-parity