Logs: freenode/#xmonad
| 2021-02-03 16:09:02 | <Solid> | Liskni_si: sounds like a good idea actually |
| 2021-02-03 16:09:03 | × | mc47 quits (~yecinem@89.246.239.190) (Ping timeout: 258 seconds) |
| 2021-02-03 16:10:08 | <Liskni_si> | (Google interviewers ask people these kind of questions, and so do interviewers anywhere where databases are involved :-)) |
| 2021-02-03 16:11:08 | <Liskni_si> | which reminds me, that if we ever get the opportunity to rewrite xmonad (like, say, if Wayland takes off), we should ditch String |
| 2021-02-03 16:11:30 | <Solid> | oh definitely |
| 2021-02-03 16:11:35 | <Solid> | Text all the way |
| 2021-02-03 16:12:18 | <Liskni_si> | right now it's not just slow, but also X11 uses String as if it was a utf-8 byte string, and that's just totally fucked up |
| 2021-02-03 16:12:40 | <Liskni_si> | not necessarily utf-8, even |
| 2021-02-03 16:14:43 | <psibi[m]> | In my setup, the most CPU intensive part seems to be xmobar. xmonad stays at 0% CPU and memory consumption for majority of the time. |
| 2021-02-03 16:16:08 | <psibi[m]> | It would be nice to observe the statistics in a more streamlined way. Does anybody here know an easy way to achieve it ? |
| 2021-02-03 16:17:55 | <Liskni_si> | that's actually an interesting observation |
| 2021-02-03 16:18:35 | <Liskni_si> | xmonad does a _lot_ of unnecessary work on every refresh (window switch, etc.) |
| 2021-02-03 16:18:52 | <Liskni_si> | yet it still consumes less CPU than xmobar, here as well |
| 2021-02-03 16:18:53 | → | cfricke joins (~cfricke@unaffiliated/cfricke) |
| 2021-02-03 16:19:16 | <Liskni_si> | and if I remember correctly, psibi[m] doesn't even have xmobar refreshing once a second like me, right? |
| 2021-02-03 16:19:53 | <psibi[m]> | Yeah, I have very less refreshing. |
| 2021-02-03 16:20:10 | <psibi[m]> | My guess is the bottleneck is in xft rendering. |
| 2021-02-03 16:20:20 | <psibi[m]> | But I don't have sufficient data or benchmark to prove it. |
| 2021-02-03 16:20:21 | <Liskni_si> | I don't have xft |
| 2021-02-03 16:20:46 | <psibi[m]> | How does your xmobar perf look like ? |
| 2021-02-03 16:21:04 | <psibi[m]> | I see frequent CPU and memory jump in my xmobar setup. |
| 2021-02-03 16:21:06 | × | davemq quits (~davemq@99-179-0-50.lightspeed.austtx.sbcglobal.net) (Quit: ZNC 1.8.2 - https://znc.in) |
| 2021-02-03 16:21:29 | <Liskni_si> | 1 minute 30 seconds of CPU time after 5 hours 20 minutes |
| 2021-02-03 16:21:39 | <Liskni_si> | xmonad is at 2:48 after 3 _days_ |
| 2021-02-03 16:22:35 | <Liskni_si> | I don't really observe significant jumps in xmobar cpu usage, it's at 0.3% most of the time and it goes up to 0.7% every few seconds when it needs to redraw the battery and temperature stuff |
| 2021-02-03 16:22:56 | <Liskni_si> | and that's not really CPU time really, most of that 0.4 is spent in ACPI |
| 2021-02-03 16:23:16 | <Liskni_si> | (maybe the kernel busyloops or something, dunno, don't care) |
| 2021-02-03 16:24:35 | <Liskni_si> | I would expect the 0.3 number to be less though, it's just rendering some text |
| 2021-02-03 16:26:33 | <Liskni_si> | if I run top -d 1 it seems the terminal consumes less cpu than xmobar :-) |
| 2021-02-03 16:26:34 | × | ChubaDuba quits (~ChubaDuba@37.112.231.139) (Read error: Connection reset by peer) |
| 2021-02-03 16:26:45 | <Liskni_si> | even though it does more |
| 2021-02-03 16:27:08 | → | ChubaDuba joins (~ChubaDuba@37.112.231.139) |
| 2021-02-03 16:30:32 | → | davemq joins (~davemq@99-179-0-50.lightspeed.austtx.sbcglobal.net) |
| 2021-02-03 16:50:03 | × | cfricke quits (~cfricke@unaffiliated/cfricke) (Quit: WeeChat 3.0) |
| 2021-02-03 17:03:55 | → | geekosaur joins (82650c7c@130.101.12.124) |
| 2021-02-03 17:09:26 | <psibi[m]> | How do you observer the 2:48 part ? I remember you mentioning it an xmobar issue which we were discussing previously, but I guess I forgot the details. |
| 2021-02-03 17:09:36 | <geekosaur> | ps? |
| 2021-02-03 17:10:46 | <geekosaur> | also, fwiw xmonad in my experience performs very poorly with hundreds of windows. not that people have that many windows normally (I discovered it through malfunction of a messaging system that created 1 window per message) |
| 2021-02-03 17:11:17 | <psibi[m]> | Ah, thanks. But for me the bottleneck is xmobar instead of xmonad. :-) |
| 2021-02-03 17:11:19 | <geekosaur> | this is likely to have as much to do with the layout using lists as it is nub vs. nubOrd |
| 2021-02-03 17:12:20 | <psibi[m]> | xmobar usage: 5:37 out of 9:37 |
| 2021-02-03 17:12:20 | <psibi[m]> | xmonad usage: 0:09 out of 9:37 |
| 2021-02-03 17:12:57 | <psibi[m]> | That's the statistics for my machine. |
| 2021-02-03 17:13:20 | <geekosaur> | iirc xmobar wakes up a lot when it doesn't need to |
| 2021-02-03 17:14:12 | <geekosaur> | like it checks some things every 1/10 second even when you use larger delays in the commands list |
| 2021-02-03 17:15:07 | <psibi[m]> | Yeah, I think that code is still there. |
| 2021-02-03 17:15:11 | <geekosaur> | it's pretty sad when I have a pair of decked-out mate-panels (which share a process) and it uses less cpu than xmobar would in my experience |
| 2021-02-03 17:15:59 | <psibi[m]> | Do you use xmobar or any other ones ? I would like to stick to xmobar because it's easy to understand the code! |
| 2021-02-03 17:16:45 | <geekosaur> | I use xmonad with mate so I run mate-panel with an xmonad-log-applet in it |
| 2021-02-03 17:20:46 | <psibi[m]> | Ah, I see. |
| 2021-02-03 17:41:47 | → | mc47 joins (~yecinem@89.246.239.190) |
| 2021-02-03 17:45:46 | <Liskni_si> | psibi[m]: the numbers I wrote here were from ps, yeah |
| 2021-02-03 17:46:40 | <Liskni_si> | psibi[m]: a few months ago when we were obsessing around the timezone refresh in xmobar I did a bit more precise measurements, but now I just looked at the "started at" and "cpu usage" columns in ps |
| 2021-02-03 17:47:30 | <Liskni_si> | geekosaur: I fixed the wakeup issue a couple months ago |
| 2021-02-03 17:48:27 | <Liskni_si> | geekosaur: it requires threaded rts and the implementation isn't as elegant as one would expect a cooperative-multitasking timer coalescing thing to be, so there probably is some overhead, but xmobar does wake up exactly once per second here |
| 2021-02-03 17:52:16 | × | geekosaur quits (82650c7c@130.101.12.124) (Quit: Ping timeout (120 seconds)) |
| 2021-02-03 17:54:52 | → | geekosaur joins (82650c7c@130.101.12.124) |
| 2021-02-03 17:58:01 | <Solid> | Liskni_si: you were right, if we need the list in normal form (not whnf), then nubOrd is slower up until like ~15 windows |
| 2021-02-03 17:58:57 | <Liskni_si> | Solid: good thing I said "two-digit number" and not "about 50" as I wanted :-) |
| 2021-02-03 17:59:08 | <Solid> | :D |
| 2021-02-03 17:59:21 | <Liskni_si> | it's been a while since my last Google interview :-D |
| 2021-02-03 18:14:17 | × | ChubaDuba quits (~ChubaDuba@37.112.231.139) (Quit: WeeChat 1.6) |
| 2021-02-03 18:30:30 | → | themc47 joins (~yecinem@89.246.239.190) |
| 2021-02-03 18:32:45 | × | mc47 quits (~yecinem@89.246.239.190) (Ping timeout: 240 seconds) |
| 2021-02-03 18:45:37 | × | themc47 quits (~yecinem@89.246.239.190) (Quit: Leaving) |
| 2021-02-03 18:45:53 | → | mc47 joins (~yecinem@89.246.239.190) |
| 2021-02-03 19:01:53 | StonedApe | is now known as Hash |
| 2021-02-03 19:18:02 | × | geekosaur quits (82650c7c@130.101.12.124) (Ping timeout: 240 seconds) |
| 2021-02-03 19:57:12 | × | sam_d quits (~sam@unaffiliated/sam-d/x-1905598) (Read error: Connection reset by peer) |
| 2021-02-03 19:57:43 | → | sam_d joins (~sam@unaffiliated/sam-d/x-1905598) |
| 2021-02-03 19:57:58 | → | geekosaur joins (82650c7c@130.101.12.124) |
| 2021-02-03 19:58:22 | × | ixian quits (~mgold@2002:4a74:ba78:1701:0:ff:fe78:6269) (Ping timeout: 265 seconds) |
| 2021-02-03 20:01:23 | → | ixian joins (~mgold@2002:4a74:ba78:1701:0:ff:fe78:6269) |
| 2021-02-03 21:10:10 | → | ADG1089__ joins (~aditya@223.236.190.35) |
| 2021-02-03 21:27:17 | × | dxld quits (~dxld@rush.pub.dxld.at) (Quit: Bye) |
| 2021-02-03 21:28:17 | × | ADG1089__ quits (~aditya@223.236.190.35) (Remote host closed the connection) |
| 2021-02-03 21:33:20 | → | endiruna joins (~endiendir@46.101.187.207) |
| 2021-02-03 21:34:06 | <endiruna> | hi! new to xmonad. coming from i3. is there someone who could share his xmobar configuration that shows workspaces and clickable? |
| 2021-02-03 21:35:29 | <Liskni_si> | endiruna: are you comfortable running xmonad and xmonad-contrib from git or do you something that works with the last release? |
| 2021-02-03 21:36:31 | <endiruna> | yes. I wanted to learn also a bit of haskell |
| 2021-02-03 21:37:39 | <Liskni_si> | in that case, https://github.com/xmonad/xmonad-contrib/blob/master/XMonad/Util/ClickableWorkspaces.hs#L29-L37 should be all you need :-) |
| 2021-02-03 21:39:02 | <Liskni_si> | (I could show you my config as well but I'm using features of xmonad-contrib that aren't merged yet) |
| 2021-02-03 21:48:22 | × | mc47 quits (~yecinem@89.246.239.190) (Remote host closed the connection) |
| 2021-02-03 21:49:24 | × | geekosaur quits (82650c7c@130.101.12.124) (Quit: Connection closed) |
| 2021-02-03 21:50:06 | × | werneta quits (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Ping timeout: 256 seconds) |
| 2021-02-03 21:50:30 | → | geekosaur joins (82650c7c@130.101.12.124) |
| 2021-02-03 21:50:50 | <endiruna> | thanks! |
| 2021-02-03 21:51:58 | → | werneta joins (~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) |
| 2021-02-03 22:06:59 | × | geekosaur quits (82650c7c@130.101.12.124) (Quit: Connection closed) |
| 2021-02-03 22:27:01 | → | ADG1089__ joins (~aditya@223.236.190.35) |
| 2021-02-03 22:34:05 | × | endiruna quits (~endiendir@46.101.187.207) (Ping timeout: 272 seconds) |
| 2021-02-03 22:35:59 | → | dxld joins (~dxld@rush.pub.dxld.at) |
| 2021-02-03 23:00:44 | → | endiruna joins (~endiendir@46.101.187.207) |
| 2021-02-03 23:11:42 | × | ADG1089__ quits (~aditya@223.236.190.35) (Remote host closed the connection) |
| 2021-02-03 23:13:27 | × | seschwar quits (~seschwar@unaffiliated/seschwar) (Quit: :wq) |
| 2021-02-03 23:18:37 | × | xaltsc quits (~xaltsc@unaffiliated/xaltsc) (Ping timeout: 260 seconds) |
| 2021-02-04 00:07:05 | × | theDon quits (~td@94.134.91.50) (Ping timeout: 240 seconds) |
| 2021-02-04 00:15:50 | → | theDon joins (~td@muedsl-82-207-239-014.citykom.de) |
| 2021-02-04 00:19:20 | × | thc202 quits (~thc202@unaffiliated/thc202) (Ping timeout: 258 seconds) |
| 2021-02-04 00:21:55 | × | notis quits (~notis@185.51.134.229) (Ping timeout: 256 seconds) |
All times are in UTC.