You are not logged in.
Pages: 1
Simply put: Conky updates my screen every second with stats. A screen update every second uses CPU.
Should I worry?
Offline
Simply put: Conky updates my screen every second with stats. A screen update every second uses CPU.
Should I worry?
Test it and see. There is a reason that conky includes this configuration variable update_interval_on_battery
On my eee, the difference between update_interval_on_battery = 1 and = 3 is about 55 minutes of battery
Last edited by skunktrader (2010-12-30 14:24:02)
Offline
Seems easy enough to test through comparison.
Offline
It does create lots of wakeups, so yes I believe it does. This lappie has a crappy battery though so I just keep it on the wire most of the time.
Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.
Offline
I kill all conky instances I don't need when I'm on battery and need to keep running as long as possible.
I don't see how an extra process keeping your CPU busy all the time would not impact battery life?
Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy
Offline
Yeah, it seems pretty obvious now...
Killing conky shaved about 1W according to powertop.
Too bad that was my clock.
I can either put a clock in my tint2 or just use the date command in a terminal, No big deal.
Offline
Pages: 1