Interview With Arjan van de Ven of Intel and Lesswatts.org
Linux Journal recently caught up with Intel's Arjan van de Ven. Van de Ven leads Intel's green Lesswatts.org initiative and is the developer of PowerTOP, one of the most acclaimed power management tools on the Linux platform.
Linux Journal: Thanks for joining us, Arjan. First off, we are curious to know what are your main duties at Intel? Do you spend most of your time with Lesswatts.org and PowerTOP or in other areas?
Arjan van de Ven: I'm leading a team of engineers that does various things, including power management and performance optimization for Linux on Intel hardware.
LJ: Do you feel that Lesswatts.org is successful thus far? If so, why? If not, why not?
van de Ven: Judging by the number of visitors, I consider Lesswatts.org a great success for users. People seem to really look for and appreciate information and tips and tricks on saving power. I look forward to more external contributions as people get more familiar with the effort.
LJ: Is there a roadmap for the future of Lesswatts.org?
van de Ven: There are various smaller and bigger projects that Intel engineers are going to work on in the future that will be part of the Lesswatts.org umbrella project; I can't disclose the specifics now, some of them are tied to features on Intel's roadmaps, other things are more general improvements to Linux power management and power savings.
LJ: What resources has Intel devoted to Lesswatts.org?
van de Ven: I'm sorry but as a matter of policy Intel does not disclose staffing or resource amounts for projects.
LJ: How optimistic are you about the possibility that tools like those found on Lesswatts.org can really make a difference in real-world power consumption?
van de Ven: We're seeing it already in distributions like the latest releases of Fedora and Ubuntu; these releases use quite a bit less power than their versions, say, a year and a half ago. (The exact numbers obviously depend on exactly what kind of hardware you're measuring it on, and what the workload is). In the commercial enterprise space the customers are much more conservative and end up consuming Linux improvements after a longer period, so most of the gain for these customers is still to come.
LJ:What prompted you to create PowerTOP, the tool you've created to help find programs that are consuming extra power when a computer is idle, thus taking advantage of the tickless Linux kernel feature?
van de Ven: Thomas Gleixner and Ingo Molnar were working on the tickless idle feature, but we weren't seeing much power savings...contrary to our expectations. It turned out user space was so incredibly busy that the OS as a whole ended up having a tick in practice. At first I started fixing individual applications, but after some time I learned the hard way that the user-space people were introducing new issues faster than I could fix them. As part of this fixing I had made some crude tools for myself (based on infrastructure that Thomas and Ingo made). I decided to turn the tools into something actually usable so that many more people (especially the developers of the software) could fix the applications.
LJ: Are there certain applications or types of applications that are the worst offenders, i.e. preventing one to take full advantage of the tickless kernel?
van de Ven: At this point, media players and certain Web applications (AJAX websites and rich content) tend to be the worst offenders. Some of it is unavoidable, but even when idle these kind of apps
tend to not behave nicely.
LJ: What is your vision for PowerTOP in the future?
van de Ven: In the next few months we'll be expanding it to track disk usage. Disks take quite a bit of power when they're in active use (at this point, more than the CPU now that the apps are fixed for that). In addition, with the advent of flash based SSDs (in devices like the Eee PC) it's also a matter of having the flash live longer, so it's two birds with one stone.
LJ: What kinds of other power or environment related issues have you been focused on lately, if any?
van de Ven: Now that the CPU side is pretty well covered, I've been looking more at other parts of the system, such as the chipset, disk and memory. Part of this ends up being device-driver work, which is harder and has a somewhat smaller reach (fix Firefox and all users benefit, fix a wireless driver and only users with that specific model of hardware benefit), but it still needs to be done as well.
LJ: What are your other computing interests besides PowerTOP?
van de Ven: I do a whole lot of different things; lately I've been looking at how to deal with the Linux kernel quality issue that keeps coming up every year (and started tracking defect reports in an automated way on http://www.kerneloops.org) and on some nasty performance behavior of Linux that really annoys me. Linux as I use it on my laptop tends to "stutter" regularly, and it's really hard to find out why, so I started creating tools to figure out what is going on (http://www.latencytop.org) and then try to fix various things in the OS to make the problem go away for me.
LJ: Thank you for the information, Arjan van de Ven. It has been fascinating to learn more about your work. We wish you continued success!
van de Ven: You're welcome.
James Gray is Products Editor for Linux Journal.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Non-Linux FOSS: Caffeine!
- Tech Tip: Really Simple HTTP Server with Python
- Doing for User Space What We Did for Kernel Space
- Parsing an RSS News Feed with a Bash Script
- SuperTuxKart 0.9.2 Released
- Rogue Wave Software's Zend Server
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide