Closed zen1tho closed 1 year ago
I feel that it is important to note that the "benchmark" I'm using is the speed of glxgears and slight lags in between changing workspaces in i3 (with picom-tryone-git)
EDIT: Here's my glxgears results (picom killed): Battery: ~5402fps Charging: ~11408fps
This isn't a bug, it's intentional behavior to account for the chemical limits of modern batteries. Pretty much every laptop (but especially one with an H-class CPU and an Nvidia GPU like the Gazelle) will need to throttle on battery. LiPo batteries have safety limits to keep them from discharging too quickly. They even have a safety "breaker" in them that completely cuts power if the battery is overdrawn, and if that breaker gets tripped, the machine usually can't be turned back on until it gets plugged into the charger. In order to prevent sudden and complete shutdowns, the power limits of the CPU and GPU must be decreased while disconnected from AC power. There is quite a bit of engineering and testing effort that goes into pushing those limits as high as they can be without risking overdraw though.
Steps to reproduce
/etc/modprobe.d/blacklist.conf
)paru -S system76-acpi-dkms-git system76-dkms-git system76-driver system76-firmware system76-firmware-daemon system76-io-dkms-git system76-power-git
(I used git versions to see if it would mitigate this issue)sudo downgrade 'nvidia-dkms=525.85.05' 'nvidia-utils=525.85.05' 'nvidia-settings=525.85.05' 'lib32-nvidia-utils=525.85.05'
system76-power graphics nvidia
system76-power profile performance
and rebootexec xrandr --output eDP-1-1 --auto --primary --dpi 144
to top of i3 configExpected behavior
Laptop to perform the same while charging and on battery.
Actual behavior
Laptop almost always outperforms battery while charging. In some cases, they are similar in performance but most of the time, the laptop performs much, much better while charging.
Additional info
I researched this issue, and some people said that you can change the setting through BIOS, but I do not see any option like that in the System76 BIOS. I get similar results while running Pop!_OS, but I never realized it was such an issue until I switched to Arch and directly saw the performance hit.