4 ms·

> So what exactly is so complex that Ethereum runs that it processes stuff so slowly? Nothing against the talented devs working at Klarna, but if they have tro

> So what exactly is so complex that Ethereum runs that it processes stuff so slowly? Nothing against the talented devs working at Klarna, but if they have trouble handling the load, they can always add a couple TB of memory or a couple hundred CPU cores. Ethereum needs to solve 100k tps while continuing to run on a Raspberry Pie on a home internet connection.

dmitriid 4y ago
> Nothing against the talented devs working at Klarna, but if they have trouble handling the load, they can always add a couple TB of memory or a couple hundred CPU cores. Ouch. Burn :) A lot of fat has been trimmed from Kred and it's now rammed into an AWS instance, but the pain is real :) > Ethereum needs to solve 100k tps while continuing to run on a Raspberry Pie on a home internet connection. To run a node you need a 2TB disc, at least 16 GB of RAM and a quad-core CPU. So, not on Raspberry Pi yet (and probably not ever).
- pa7x1 4y ago
  https://twitter.com/ethereumonarm/status/1432251814402002948?lang=en https://twitter.com/ethereumonarm/status/1432251814402002948... This is just an example, there is plenty other hobbyists doing so. And here detailed instructions for you to try at home: https://docs.rocketpool.net/guides/node/local/prepare-pi.html#mounting-the-ssd https://docs.rocketpool.net/guides/node/local/prepare-pi.htm...
  - dmitriid 4y ago
    And then you actually go into the docs.... And: oh, 8 GB RAM should work, but let's have a 32 GB swap. The CPU should be fine, but let's overclock it. Oh, you shouldn't use Geth to ensure ecosystem health, but all clients except Geth require at least 16 GB of RAM. And geth will eat all of your disk spce if you're not careful. So, for a single combination (Geth + Nimbus) it may just be possible to run this tower of babel on a Raspberry Pi. And.... The only thing it will be doing is... nothing, really.

dmitriid 4y ago

> Nothing against the talented devs working at Klarna, but if they have trouble handling the load, they can always add a couple TB of memory or a couple hundred CPU cores. Ouch. Burn :) A lot of fat has been trimmed from Kred and it's now rammed into an AWS instance, but the pain is real :) > Ethereum needs to solve 100k tps while continuing to run on a Raspberry Pie on a home internet connection. To run a node you need a 2TB disc, at least 16 GB of RAM and a quad-core CPU. So, not on Raspberry Pi yet (and probably not ever).

pa7x1 4y ago
https://twitter.com/ethereumonarm/status/1432251814402002948?lang=en https://twitter.com/ethereumonarm/status/1432251814402002948... This is just an example, there is plenty other hobbyists doing so. And here detailed instructions for you to try at home: https://docs.rocketpool.net/guides/node/local/prepare-pi.html#mounting-the-ssd https://docs.rocketpool.net/guides/node/local/prepare-pi.htm...
- dmitriid 4y ago
  And then you actually go into the docs.... And: oh, 8 GB RAM should work, but let's have a 32 GB swap. The CPU should be fine, but let's overclock it. Oh, you shouldn't use Geth to ensure ecosystem health, but all clients except Geth require at least 16 GB of RAM. And geth will eat all of your disk spce if you're not careful. So, for a single combination (Geth + Nimbus) it may just be possible to run this tower of babel on a Raspberry Pi. And.... The only thing it will be doing is... nothing, really.