Describe the bug
On my desktop workstation with an 8-cores Xeon CPU and AMD Radeon R9 270 on GNOME 50.1's Wayland session, when typing in the main SearchEntry widget ("Filter Units by their Names"), I can feel it blocking the mainloop / eating the CPU on every character I'm typing. This can be seen through gnome-system-monitor too while you are typing in SysD manager's searchentry, where it can easily eat up to half of one CPU core:
Are you connected to the SearchEntry widget's search-changed signal (which has a default 150ms delay before activation to avoid spamming too much), or are you accidentally connecting to a different widget signal?
Expected behavior
It should be butter-smooth.
The package format
Additional context
If filtering/searching is too expensive for a 150ms delay to emit the search-changed signal, then please consider setting the SearchEntry widget's search-delay to a value much higher than 150ms (in expensive situations, I recommend 300 to 500 miliseconds) to delay that signal. Same logic as in:
I would recommend this for any location where you do live expensive search/filtering as you type.
Describe the bug
On my desktop workstation with an 8-cores Xeon CPU and AMD Radeon R9 270 on GNOME 50.1's Wayland session, when typing in the main SearchEntry widget ("Filter Units by their Names"), I can feel it blocking the mainloop / eating the CPU on every character I'm typing. This can be seen through gnome-system-monitor too while you are typing in SysD manager's searchentry, where it can easily eat up to half of one CPU core:
Are you connected to the SearchEntry widget's
search-changedsignal (which has a default 150ms delay before activation to avoid spamming too much), or are you accidentally connecting to a different widget signal?Expected behavior
It should be butter-smooth.
The package format
Additional context
If filtering/searching is too expensive for a 150ms delay to emit the
search-changedsignal, then please consider setting the SearchEntry widget'ssearch-delayto a value much higher than 150ms (in expensive situations, I recommend 300 to 500 miliseconds) to delay that signal. Same logic as in:I would recommend this for any location where you do live expensive search/filtering as you type.