Too many wakeups (using ghc-7.4.1) about xmobar HOT 11 CLOSED

I've been using -threaded -with-rtsopts=-V0 to make xmobar/xmonad less watt-hungry for a few years. I'm not sure how safe this is and I'd be hesitant to just put it into xmobar.cabal, but I've had it there for years and it hasn't caused problems. But it's kind of sad that this is still a problem with GHC 8. :-/

from xmobar.

However installing xmobar with cabal install xmobar
--ghc-options=-threaded doesn't make a difference - xmobar still
produces around 75 wakups/s.

Does giving cabal install the with_threaded flag solve the issue?

cabal install xmobar --flags=with_threaded

from xmobar.

Not any better here with 7.6.2, compiled with '--flags="with_mpd with_dbus with_inotify with_utf8 with_xft with_threaded"' and with '--ghc-options="-threaded"', too. Around 100 events per second, according to powertop. :(

from xmobar.

this is with the git version of xmobar, right? does is happen with 0.16?

from xmobar.

The actual command I issued to get xmobar was: 'cabal install xmobar --flags="with_mpd with_xft with_utf8 with_dbus with_inotify with_threaded" --ghc-options="-threaded"', so no, not the git version. ;)

from xmobar.

Ubuntu 12.04/amd64 (ghc-7.4.1-1ubuntu2), I've recopiled xmobar with 'cabal install xmobar --ghc-options="-threaded', restarted, and wakeups/s dropped from 30 to 10 both in xmobar and xmonad.

from xmobar.

from xmobar.

Perhaps. But then haven't been any reports of too many wakeups for the last 2 years (mostly because intel realized software developers are idiots and managed to fix this in the hardware) so maybe not worth the trouble. :-)

from xmobar.

I'm using xmobar 0.24.3 compiled using ghc 8.0.2. I set the threaded flag to default True, cabal installed, (checked that sha1sum $(which xmobar) changed), still lots of wakeups (~100/s). Nothing unusual in xmobarrc..

from xmobar.

from xmobar.

this change is in 0.24.4 and it works for me, so i'm closing the bug. feel free to reopen as needed.

from xmobar.