by impure-aqua | 2025-09-22 14:08:33+00:00
I don't think Framework will be able to compete on efficiency with their design philosophy.

The NVMe disk is swappable, which means it has its own controller which manages power management itself. I did my research to pick an efficient SSD and ended up with a Lexar NM790. It tops Tom's efficiency charts and comes in third place for lowest idle power consumption [0]. This is still ~0.8W at idle. On a 60Wh battery an idling drive alone will kill the battery in 3 days.

Now technically there is the APST (Autonomous Power State Transition) feature in the NVMe specification. Is there some lower APST power state that can get the power draw down? Potentially, but that is a feature well beyond the purview of any SSD reviews I have seen, so I don't know- does this drive have reliable and well-implemented APST state support? How does this interact with the platform-specific sleep state implementation, which presumably wakes the disk sometimes to do some Modern Standby features- how often is it spending time in that 0.8W state versus lower? This can vary between board rev or BIOS version certainly. Beyond the actual drive configuration and ACPI interaction, there is also kernel interaction. Do certain drives behave poorly with Linux? Etc etc.

On the RAM side of things, they are using DDR5 and not LPDDR5. There is a lower voltage on LPPDR5 which is a constant inefficiency, but also LPDDR5 has dynamic voltage scaling and dynamic frequency scaling. There is also technically some voltage drop across the SODIMM connector which you don't need to contend with when you solder RAM, which would be a constant source of loss, but I am not sure how significant that is.

Beyond this you have different behaviour for every model of RAM. This post on the Framework forum shows the user could get 7.82 days of suspend time with the HMCG66MEBSA092N DDR5-4800MHz 16GB kit whereas only 2.25 days with the CT2K48G56C46S5 DDR5-5600MHz 96GB kit [1]. Consider that there are effectively infinite combinations of memory people can run, and even inside a model series, vendors can swap their chip providers, etc. Which kits give the best battery endurance? I can't tell you.

Now someone could certainly embark on a long adventure to test different drives, RAM kits, and measure their performance, recommend tunables for the Linux kernel you want to set for each particular set of hardware, etc. But this is effectively what Apple is doing for you with the MacBook. They are choosing their memory supplier, their flash supplier, and integrating as much as possible into their SoC with presumably an entire team focused on extracting the most efficient behaviour out of both.

Consider this same thing extends to display behaviour (beyond VRR support, which I believe Framework has now, you also have local dimming behaviour to tune on the MBP), wireless behaviour, all sorts of embedded controllers that Apple can wrap inside the SoC that I probably wouldn't think of... I don't see how a modular system like Framework can achieve anything close to the idle efficiency of a MacBook.

[0] https://www.tomshardware.com/reviews/lexar-nm790-ssd-review/...

[1] https://community.frame.work/t/impact-of-ram-density-on-susp...