Not much of one, but for a while I was playing with multiple distros trying to find the best possible power management for my laptop. (XPS 13 9380.)
Clear did better than the Ubuntu installation that came with it -- but a dead octopus would have done better than that. It was sitting at 6W for non-CPU-intensive work, and was also noticeably snapppier. Windows on the same hardware sits at 8W when idling; same as Ubuntu.
More recently I've tried Arch, though. Which somehow got that same workload down to 3.3W, albeit with a lot of adjustments... that didn't seem to affect performance, but did affect power use, clearly.
It's just too bad that all of this optimization goes out the window if I fire up a browser, but I've had a fun time finding ways to avoid that.
Apart from that, obviously Clear's software repository is far more limited than Arch's, and it also seems harder to contribute to. I don't think that problem will be going away soon.
If you have a SSD you can be aggressive on the disk suspend timeout, as there's no spin up/down wear issue as with mechanical disks.
With this the battery life is good enough that I never felt the need to optimize further.
- Force deep sleep mode, as s2idle doesn't work.
- Set the ASPM policy. To anything. Basically the default doesn't work. (I went with 'powersave', obviously.)
- Run powertop --auto-tune on boot.
- Set the cool-bottom thermal profile, but that's just to make it work as a lap top.
- Run a BIOS upgrade. :V
(fwupdmgr did the whole job for me~)
Some modules also have blacklists that prevent certain power saving modes from being enabled. This is true for the snd-hda-intel module to prevent a well known popping sound. Since disabling the blacklist, I haven't encountered the issue however YMMV. Similarly to enable ASPM on the PCIE bus, I've had to force it via a kernel parameter.
With regards to the GPU, I noticed my Intel GPU can scale its frequency between 300mhz and 950mhz but the default minimum was set to 350mhz. Other such tweaks such as enabling frame buffer compression [4], can save you a few more watts.
While the Linux defaults does its best to be suitable across different hardware configurations, you'll have to meddle with many parameters to get it customised to your configuration, and that could bring some instability with it so exercise some caution.
Oh, and also be mindful of the apps you run. The Great Suspender for Chrome can save you some watts, cpu and memory by suspending tabs that are not in use. And switching to a light desktop such as Sway or i3 can also do wonders.
As I type this, my battery is reporting a draw of 3.1 watts, 30% battery remaining with 4:40 of operating time at the current workload.
[1] - https://wiki.archlinux.org/index.php/TLP
[2] - https://hansdegoede.livejournal.com/18412.html
[3] - https://wiki.archlinux.org/index.php/Power_management#SATA_A...
[4] - https://wiki.archlinux.org/index.php/Intel_graphics#Framebuf...
Using Arch often gives me advance warning that my apps will break on users machines due to changes in libraries. I see the changes first and can add compatibility for the new library version such that it's fixed before affecting my users.
I love it as a daily driver.
Totally agree that it's a great daily driver. It has EVERYTHING!
I'm assuming you used Powertop on Linux.
For Windows, I simply let the laptop run until it had used 50% of the battery. Watts = Joules / second.
On Linux, I used the same methodo to calibrate against powertop. (But found less than 5% of discrepancy anyway.)
If we are talking about battery-life at least.
In fact, what mobile device manufacturers have learned is that the best way to save power is to ramp up power to complete a non-IO task in as little time as possible then go back to a lower TDP as that is where peak efficiency (rather than minimal consumption) lies.
I think most people are interested in their battery life when they are measuring their battery life.
Numbers you get while plugged in won't have any relevance to battery life or performance. That even applies to mobile devices, despite their learnings.
You should use the same methodology for both.
That estimate is usually accurate, but it can drift a bit over time if you never fully recharge or discharge the battery. Also, when the battery gets old it starts having trouble delivering full current when mostly discharged, which is why you'll sometimes see shutdowns at 5-15% remaining.
ext4 doesn't detect corruption. How am I supposed to trust it?
My Dell has an Sk Hynix NVMe drive that apparently doesn't have safe write on power failure. I know because it somehow woke up in my bag and ran the laptop battery down to 0.
BTRFS was not happy with the state of anything on the drive. I was able to do a rescue copy and verify it with my backups, so after a full restore everything turned out OK.
I get what you're saying about the filesystem. Personally, I use par2 for the most important things (photos).
I got the laptop to have well-supported hardware, not because I was expecting a lot of help from Dell.
And no, it seems they didn't. They haven't forced deep sleep, for example.
I'd urge some caution. It depends on your use case and the accuracy requirements you have. Clear Linux gets a chunk of its speed boosts by using compiler optimisations that most distributions won't touch because of the possibility they'll reduce accuracy and move outside the bounds of various standards, e.g. --ffast-math. Clear Linux also sets it so that by default when you go to compile stuff, it ends up picking up their "optimised" set of compiler flags too.
It works, it's fine, it's fast. Just make sure you know what you're getting and what the consequences for your software might be (I'm sure most people _don't_ have strict IEEE standards to care about, for example)
Most of the useful apps are available via flathub, which it comes with so you just install slack, vscode, etc. that way.
Also, its package manager forces you to install "bundles" of somewhat related packages rather than just the specific packages you want and their deps. Maybe I'm missing something, but I find this very odd.
This is a common misconception. It's not built with ICC, it's built with GCC (and some parts maybe with Clang).
When did you try Clear? They have about 6200 packages now, but I'm not sure if that's still "limited" in relative terms.
Last time I tried it was a couple of months ago. I don't recall what it was missing, but it was some core part of my normal python development environment.
Also, NVIDIA CUDA drivers didn't work. Not sure who's fault that is. Probably both NVIDIA and Intel's.
All in all, it did boot quickly on AWS, but it was not a fun time at all.
This brings me back to the heydays of Sun Microsystems where they controlled both the hardware (SPARC) and the operating system (Solaris). Sun didn't hesitate to use this to their advantage. With Clear Linux, I see Intel doing some very similar things. Yes, this was just a story about boot time, but it led me to take a look at Clear Linux and it looks like it could be a star. I'm interested in how much more performance their distribtuion is able to squeeze out. I'm also wondering how they're dividing their focus here and what high notes they're trying to achieve.
At a strategic level, I'm assuming that they're wanting to distinguish themselves from ARM? Are they looking to create a well-tuned reference for other Linux distributions on Intel to adopt? At a tactical level, I see they're focusing on performance, availability (which boot time would be a function of)... but are they tweaking for other things such as reliability? Fault tolerance?
Until now, Clear Linux wasn't even on my radar. Today, it is. Anyone have some experiences with this distro (for better or worse) that they'd like to share?