4 ms·
sure! bare-metal would be awesome. But isn't it a shame not to take advantage of all the virtualization/containerization goodies out there? After all, the virtu
by _ananos_ 7y ago
sure! bare-metal would be awesome. But isn't it a shame not to take advantage of all the virtualization/containerization goodies out there? After all, the virtualization overhead nowadays is only referring to I/O (network & storage). CPU/MEM are being virtualized using hardware extensions at (near-)native speeds.
- Havoc 7y ago>CPU/MEM are being virtualized using hardware extensions at (near-)native speeds. Is that really true for rasp level gear? Haven't tested it but my gut feel tells me the hit is sizable. Anyway - don't let that dissuade you from the mission. Container goodies on a rasp is a grand idea...just don't think it's quite as hit free as the article suggests ;)
- _ananos_ 7y agodefinitely! that's our initial goal. Quantify the penalty and examine the trade-offs. Clearly, virtualizing workloads on such devices with standard VMMs/hypervisors isn't ideal. And we're working towards this direction; playing with the systems stack is what makes us tick, so, it will be a fun and (hopefully) useful adventure :D
- Havoc 7y ago>Quantify the penalty and examine the trade-offs. If you do have numbers available I'd love to see a write-up on what the real world hit is. I used to run a rasp3b for home server but that just wasn't punchy enough (crappy fake gigabit etc). So my old gaming laptop became a server w/ docker etc. But itching to justify a rasp 4. Anyway...thanks for exploring 64...thought the 32 on rasp 3 was unfortunate.
- _ananos_ 7y agowill do -- that was only a high-level run to make sure there's enough compatibility with our framework & tools to move forward. stay tuned ;)
- bjoli 7y agoI have a raspberry pi 4. That thing runs HOT. 64c idle (44c above ambient) without any case, but with a PoE hat and disabled fan. The PoE hat makes attaching a proper heat sink (or using the flirc case) impossible, so I have now rolled my own using copper coins. I am not comfy with letting my pi run that hot 24/7, and I don't want active cooling. I bought a rock pi 4 which has a PoE hat that can be combined with a HUGE heat sink, and there I have no heat issues at all. There are cases you can use when you don't have a PoE hat, but the original pi 4 case almost throttles the pi at idle.
- Dork1234 7y agoI have been testing a rpi4 and comparing it to the rpi3. The Rpi4 is actually the first Pi that is usable as a desktop computer, but have seen thermal issues like you. Many the early reviews have only done short tests with the cover off. The thermal CPU throttling on the RPI4 is huge, while the RPI3 might slow things down 50-30%. The RPI4 will slow down to 100%. In the case I tested the RPI4 was running close the RPI3 speeds. I don't think a heatsink or CPU fan is needed there just not enough heat being generated to warrant the expense.I have had good luck with running the RPI with just the cover off, and some sort of air circulation in the room. I have been trying to figure out the cheapest way to cool the RPI4, I am thinking a single slow 5V fan blowing across the card would be the best solution. This would also cool off the VLI, and take up less room on the card. I am just hoping someone will make the case, fan combination the works at a good price point. If things get too pricey then other SBC look very interesting. I am really disappointed the thermal issues were not considered. A simple fan header like on UDOO boards, or an official case with space and air flow so a heat-sink could actually work would make me feel a lot better.
- franciscop 7y agoNo it's not... Containers "goodies" serve a purpose, but they also bring a big number of disadvantages to the table! It's not all fun and games in container world. We definitedly need better build tools, but I don't think containers are the solution here, or at least not the only solution.
- _ananos_ 7y agoagree, I'm just talking about the flexibility to build & deploy a workload in any device (cloud / edge). Think of it like "building your own buildroot image" vs. "docker build" based on busybox or alpine. In the first case you'll end up with exactly what you want, but you'll spend quite some time building it; in the latter case you'll have to mix & match various other stuff, but you'll end up executing the actual application a lot faster.