The Raspberry Pi 4 has been out for about 6 months, and early reviews made it clear that the best option was just to sit back and wait for it to get a bit more stable. That’s happened, so now I’m going to dig into one and see what it looks like as yet another light desktop system!
The issue is firmware-dependent; most devices will work just fine if you force-enable UAS, some refuse to work like yours - some of my Seagate 5TB drives in one color work fine, some don’t work at all - slightly different firmware revisions, but same ven/devID. It’s a bit of a nightmare.
2019-12-16 by Russell Graves
Thanks - that’s some useful background! I suppose I should try a few different enclosures and see how performance differs on them with/without UAS.
I’ve seen it. If your workload is running the Dhrystones benchmark all day long, absolutely, build a 64-bit version.
What that set of benchmarks misses, IMO, is that 64-bit binaries generally have a larger memory footprint because of the increased pointer size - and on a RAM limited device, that can really hurt things as well. ARMv8 in aarch64 mode is definitely nicer to work with, and has better performance, /in some cases/. But to run a few benchmarks and then assert blindly that the system should be 64-bit… that’s not how you do full system benchmarking/analysis.
It’s on my list of things to poke with, just fairly far down.