Language Selection

English French German Italian Portuguese Spanish

How much power does KDE need?

Filed under
KDE

Honestly, I just love hacking while traveling by train - no IRC, no ICQ, no email that steals attention. However, most of the time I don't sit near a power supply socket so my laptop runs from battery. How much do you need for running KDE? I don't mean CPU or RAM ressources, but battery power. I know that you can enhance the battery lifetime by installing more RAM into your laptop - so that the hard disk has less work to do. But how much could you save by not running KDE ?

And I had time to figure out. I've fixed busy-looping in KDE-applications already in the past, but it seems there are new offenders added to our tree on a daily basis. Even if those busy-looping applications (with short timeouts) never appear as significant in the top output - they eat processing time.. and power. For my laptop, running KDE (not doing any user interaction) requires about 1.2 W/h. Thats 10%. With other words, I could hack about 10% longer if those are fixed. Thats a lot, so I started stracing to find the worst offenders. And the hitlist is:

  • artsd. No further comment necessary, its the first thing I kill (or don't even install) anyway.

  • kded (with dnotify it seems to busy-loop due to debug-output<->directory changed trigger loop)
  • klaptopdaemon. The code just does horrible stuff, including installing event listeners everywhere for no reason. Second thing to kill if you actually use a laptop.
  • kicker. One reason is the clock, which busy-loops even if nothing is to be expected to be done. But its doing a lot more, I haven't quite figured out yet what it does, but its definitely unnecessary as long as there is no user interaction.

Over the next few weeks I might try fixing those worst offenders. Any help with that is highly appreciated.

Source.

More in Tux Machines

Games and CrossOver

Red Hat and Fedora

Android Leftovers

Leftovers: OSS and Sharing

  • CoreOS Tectonic Now Installs Kubernetes on OpenStack
    CoreOS and OpenStack have a somewhat intertwined history, which is why it's somewhat surprising it took until today for CoreOS's Tectonic Kubernetes distribution to provide an installer that targets OpenStack cloud deployments.
  • Docker and Core OS plan to donate their container technologies to CNCF
    Containers have become a critical component of modern cloud, and Docker Inc. controls the heart of containers, the container runtime. There has been a growing demand that this critical piece of technology should be under control of a neutral, third party so that the community can invest in it freely.
  • How Blockchain Is Helping China Go Greener
    Blockchain has near-universal applicability as a distributed transaction platform for securely authenticating exchanges of data, goods, and services. IBM and the Beijing-based Energy-Blockchain Labs are even using it to help reduce carbon emissions in air-polluted China.
  • An efficient approach to continuous documentation
  • The peril in counting source lines on an OSS project
    There seems to be a phase that OSS projects go through where as they mature and gain traction. As they do it becomes increasingly important for vendors to point to their contributions to credibly say they are the ‘xyz’ company. Heptio is one such vendor operating in the OSS space, and this isn’t lost on us. :) It helps during a sales cycle to be able to say “we are the a big contributor to this project, look at the percentage of code and PRs we submitted”. While transparency is important as is recognizing the contributions that key vendors, focus on a single metric in isolation (and LoC in particular) creates a perverse incentive structure. Taken to its extreme it becomes detrimental to project health.
  • An Open Source Unicycle Motor
    And something to ponder. The company that sells this electric unicycle could choose to use a motor with open firmware or one with closed firmware. To many consumers, that difference might not be so significant. To this consumer, though, that’s a vital difference. To me, I fully own the product I bought when the firmware is open. I explain to others that they ought to choose that level of full ownership whenever they get a chance. And if they join a local makerspace, they will likely meet others with similar values. If you don’t yet have a makerspace in your community, inquire around to see if anyone is in the process of forming one. Then find ways to offer them support. That’s how we do things in the FOSS community.
  • The A/V guy’s take on PyCon Pune
    “This is crazy!”, that was my reaction at some point in PyCon Pune. This is one of my first conference where I participated in a lot of things starting from the website to audio/video and of course being the speaker. I saw a lot of aspects of how a conference works and where what can go wrong. I met some amazing people, people who impacted my life , people who I will never forget. I received so much of love and affection that I can never express in words. So before writing anything else I want to thank each and everyone of you , “Thank you!”.
  • Azure Service Fabric takes first tentative steps toward open source [Ed: Microsoft Peter is openwashing a patent trap with back doors]
  • Simulate the Internet with Flashback, a New WebDev Test Tool from LinkedIn
  • Mashape Raises $18M for API Gateway Tech
    Casado sees Mashape's Kong API gateway in particular as being a particularly well positioned technology. Kong is an open-source API gateway and microservice management technology.
  • PrismTech to Demonstrate Open Source FACE 2.1 Transport Services Segment (TSS) Reference Implementation at Air Force FACE Technical Interchange Meeting
    PrismTech’s TSS reference implementation is being made available under GNU Lesser General Public License (LGPL) v3 open source license terms.
  • How Open-Source Robotics Hardware Is Accelerating Research and Innovation

    The latest issue of the IEEE Robotics & Automation Magazine features a special report on open-source robotics hardware and its impact in the field.