3 ms·
It's too bad there's no logical way to redesign the module to allow it to talk to an external memory module, while keeping its simple SODIMM form-factor. You c
by derefr 10y ago
It's too bad there's no logical way to redesign the module to allow it to talk to an external memory module, while keeping its simple SODIMM form-factor.
You could put some (much-slowed-down) memory on the SMI GPIO pins, though: you'd be able to access it "through" DMA to main memory, as if the CPU had a memory-banking architecture. (It'd probably only operate at a similar speed to that of eMMC, though; at that point, if you're running a regular OS, you may as well just put some Flash on the eMMC pins and tell the OS to treat it as a swap partition.)
I think the "idiomatic" thing to do here, though, is to not think of the rPi as a computer that needs more RAM, but rather as a fixed amount of RAM with some compute attached. Want more RAM? Plug more rPis into your board and cluster them together into a NUMA "backplane" of rPi "blades", like this:
• https://www.raspberrypi.org/forums/viewtopic.php?f=98&t=144595 https://www.raspberrypi.org/forums/viewtopic.php?f=98&t=1445...
• http://hackaday.com/2016/01/25/raspberry-pi-zero-cluster-packs-a-punch/ http://hackaday.com/2016/01/25/raspberry-pi-zero-cluster-pac...
Some applications—an RDBMS comes to mind—wouldn't distribute very well on such a setup, but Redis would run quite nicely (and concurrently!) Of course, there'd still be some restrictions: you'd not be able to have a single key with >1GB size. But if your data-set is a power-law distribution with the largest keys being <100MB, it'd work great.