diff options
| author | Sibi Prabakaran <sibi@psibi.in> | 2020-06-05 16:55:52 +0530 |
|---|---|---|
| committer | Sibi Prabakaran <sibi@psibi.in> | 2020-06-05 16:55:52 +0530 |
| commit | 878db39080607ba476ba8d8f547ad28259efb6a9 (patch) | |
| tree | 2458ce512885d6ca527e14e9c8751458e4afe320 /xmobar.cabal | |
| parent | b15bb7c20b11a9f148c4757caba7167ee66492fc (diff) | |
| download | xmobar-878db39080607ba476ba8d8f547ad28259efb6a9.tar.gz xmobar-878db39080607ba476ba8d8f547ad28259efb6a9.tar.bz2 | |
Optimize date plugin
We avoid calling getTimeZone for each of the time the date has to be
updated. Instead, it's computed once at the start and re-used for each
invocation.
Looking at the implementation of 'getTimeZone', we can see that it's
very expensive:
https://www.stackage.org/haddock/lts-15.15/time-1.9.3/src/Data-Time-LocalTime-Internal-TimeZone.html#getTimeZone
It calls a C FFI each time to get the time
zone (getTimeZoneCTime). This is something which we can avoid and the
MR implements that.
I have been using my xmobar with this patch and the result has been
quite good. My xmobar CPU usage has used to hit 3~7%
intermittently. With this MR, It hits only 0.7% intermittently which
is nice. :-)
Diffstat (limited to 'xmobar.cabal')
0 files changed, 0 insertions, 0 deletions