On Tue, 19 Sep 2017 05:43:03 -0700 Marc MERLIN <marc_...@merlins.org> said:

> I rebooted my laptop, e21 isn't taking 100% CPU anymore, but it's still
> a battery pig:
> Power est.      Usage      Events/s     Category       Description
>   6.49 W    113.0 µs/s     600.8        Process        /usr/bin/enlightenment
> 
>   PID USER      PR  NI  VIRT  RES  SHR S  %CPU %MEM    TIME+
> COMMAND 16811 merlin    22   2  828m  81m  45m S  36.6  0.3   5:50.42
> enlightenment 
> 
> I don't have any fancy options that I know of.
> I just switched from OpenGL rendering to Software rendering. Seems to
> make no difference.
> 
> Disabling composite effects makes no big difference either.
> 
> I'm just about ready to downgrade back to 0.18.6, I can't have a WM that
> sucks so much CPU and battery.
> 
> Any idea what could be causing this and how to get around it?

could be many things. what else is waking up? didn't you just have drm vsync
issues? could possibly still be happening. here is what i see:

The battery reports a discharge rate of 2.52 W
The power consumed was 49.8 J
The estimated remaining time is 17 hours, 3 minutes

Summary: 80.7 wakeups/second,  0.0 GPU ops/seconds, 0.0 VFS ops/sec and 1.0% 
CPU use

Power est.              Usage       Events/s    Category       Description
  2.58 W      0.3 pkts/s                Device         Network interface: wlan0 
(ath10k_pci)
  569 mW    100.0%                      Device         USB device: 
usb-device-04e8-a00a
 65.6 mW      6.4 ms/s      18.1        Process        [PID 534] 
/usr/local/bin/enlightenment
 26.7 mW    406.3 µs/s      14.6        Timer          tick_sched_timer
 14.2 mW    101.1 µs/s       8.1        Process        [PID 8] [rcu_preempt]
 14.0 mW    132.2 µs/s       7.9        kWork          gc_worker
 8.60 mW    374.2 µs/s       3.9        Interrupt      [0] HI_SOFTIRQ
 7.54 mW    685.1 µs/s       2.2        Process        [PID 331] 
/usr/lib/xorg-server/Xorg -nolisten tcp vt07 -auth /var/run/slim.auth

so basically it's fine. there is some polling of cpu freq and temperature, some 
battery notifications.... but really its quick wake and sleep as any render 
will invariably involve deferring the rendering for the next vsync. stracing 
shows e asleep for most of a second and eeze is forcing a poll every second on 
the temperature sensor. i unload temperature module and e will stay asleep for 
2-3 or 4 secs at a time then wakeup to a battery/power supply event and go 
check battery status. ymmv based on your acpi dsdt and how often battery acpi 
events happen, but the wakeups you see above are really only like 1 or 2 per 
sec. i think it's counting a blocking syscall like a read() of a /sysfs node or 
a write+read from pipe (vsync event from vsync thread to mainloop), actually 
strace e with timestamps and see. it may be counting selects that in the loop 
run "poll to see if events came in while we were reading them" or the thread 
selects etc. so take that number of wakeups with a grain of salt.

FYI i had my GPD pocket 7 (my mini 7" baytrail laptop) run for 22hrs without 
suspending (screen on lowest brightness level, wifi connected)... e of course 
running. when e is animating expect a lot of wakeups - at least 2-3 maybe 4x 
the actual framerate due to the above (the wake it's measured). another sample 
of battery life: galaxy book 12, 50% brightness with e just idling:

The battery reports a discharge rate of 2.29 W
The estimated remaining time is 18 hours, 30 minutes

Power est.              Usage       Events/s    Category       Description
  2.57 W      0.5 pkts/s                Device         Network interface: wlan0 
(ath10k_pci)
  572 mW    100.0%                      Device         USB device: 
usb-device-04e8-a00a
 50.1 mW      4.9 ms/s      12.8        Process        [PID 534] 
/usr/local/bin/enlightenment
 18.1 mW    265.5 µs/s       9.2        Timer          tick_sched_timer

So... actually look into what is waking things up. fast polling times for 
gadgets like temp, cpufreq etc. will use more power. temperature if using udev 
(eeze) can wake up more often.

if you have terminals with blinking cursors... that's not going to help much... 
disable blinking. :)

> Thanks,
> Marc
> -- 
> "A mouse is a device used to point at the xterm you want to type in" - A.S.R.
> Microsoft is to operating systems ....
>                                       .... what McDonalds is to gourmet
> cooking Home page: http://marc.merlins.org/                         | PGP
> 1024R/763BE901
> 
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> enlightenment-users mailing list
> enlightenment-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/enlightenment-users
> 


-- 
------------- Codito, ergo sum - "I code, therefore I am" --------------
Carsten Haitzler - ras...@rasterman.com


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
enlightenment-users mailing list
enlightenment-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-users

Reply via email to