Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dramatically CPU usage on high resolutions (Blur operation) #52

Open
undiabler opened this issue Nov 28, 2020 · 2 comments
Open

Dramatically CPU usage on high resolutions (Blur operation) #52

undiabler opened this issue Nov 28, 2020 · 2 comments

Comments

@undiabler
Copy link

Platform: Archlinux 5.9.10, i3wm

GPU, drivers, and screen setup: Nvidia Titan RTX, nvidia-drivers 455.45.01-2, one monitor 2560x1440 resolution

Compton version: git-v0.1_beta2-95-g241bbc5-2018-02-22 from aur

Compton configuration: default configuration with glx backend

Steps of reproduction

  • open terminal with blured background
  • open application like htop
  • move arrows up and down to update window state
  • watch your CPU dying =)

Expected behavior

CPU usage should not take half of system resources.

Current Behavior & Other details

CPU usage takes half of system resources on blur operation.
compton-blur

@tryone144
Copy link
Owner

The implementation you are using contains known bugs and is based on the now-unmaintained compton.
Please try the improved implementation in the active fork picom. You can install the latest development version on Archlinux with the picom-git package.

You might have to update your configuration though as some options have been deprecated and removed. You can use the dual-kawase blur-algorithm with --experimental-backends --backend glx --blur-method dual_kawase --blur-strength 7.

@undiabler
Copy link
Author

Thanks a lot. Will this implementation be maintained in future?
For now I have only one suggestion to add some deprecation block with link to picom in readme.
Its really hard for now to figure out where is actual maintained project.
Picom works good for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants