One of the challenges in mobile computing is battery life. It's hard to be productive with a dead battery, so IT personnel and users alike need to think about maximising run time between charges.
Optimising the power conservation settings of a mobile computer or communicator, including dimming the display when on battery, turning off the display and hard drive after a pre-set period of time, suspending (keeping memory alive but the computer otherwise powered down) and hibernating (writing the image of main memory to disk for later resumption) help in getting the most out of any given charge.
And there are also power conservation settings in most Wi-Fi adapters that (at first glance, anyway) are intended to allow a high degree of control over the power consumed by the wireless network interface card (NIC) found in almost all notebooks and many handhelds as well. In gross terms, wireless power conservation involves turning off the radio, synchronously or asynchronously with the fixed infrastructure, for a portion of time — a technique used in various forms on essentially all production wireless systems today, including WANs. But this technique motivates an interesting and fundamental question: do Wi-Fi power-conservation techniques, when enabled, actually save a meaningful amount of energy or have any negative impact on throughput?
We set out to define a simple test to answer these questions as they pertain to 802.11's Power Save Mode (PSM), the most common form of Wi-Fi power saving implemented today. We do note that there are several new power saving mechanisms defined for 802.11n gear, but we have not found those to be widely implemented, so we could not assess those at this juncture.
Vendors have delivered a number of PSM variants, with the primary difference being how quickly and how often the adapter wakes up. Having a NIC wake up faster could negatively affect power consumption, the fundamental tradeoff in this strategy, although this could theoretically improve throughput. The opposite of PSM is Constantly Awake Mode (CAM), in which PSM is disabled. Our test compared various forms and implementations of PSM against CAM and, for good measure, a wired Gigabit Ethernet baseline test.
Using PSM in our tests produced only a marginal benefit in terms of battery life (and was even slightly worse than CAM in one test). In terms of throughput, the results ranged from marginally positive to having a very negative impact on throughput in two cases tested
Bottom line: PSM isn't likely to be of any value in contemporary implementations, and may even hurt performance.
We contacted all vendors whose products were included in this test regarding the results. Only Broadcom's PR department would comment, saying that its internal testing showed that battery life gains from PSM implementations in notebooks varies between brands, sometimes showing that PSM can maximize battery life with no impact on throughput.
Computerworld Member Login
Beyond Virtualisation - The Roadmap to 2012
CIO Breakfast Briefing
8:30am - 10:30am
Brisbane | 22 July | Sofitel Brisbane
Sydney | 23 July | Four Seasons Hotel
Canberra | 24 July | The Hyatt
Attend and discover:
- What happens after virtualisation
- The benefits automation drives
- When automated infrastructures will emerge
- What the roadmap to 2012 looks like
- How to deliver an automated architecture
- How to maximise your investment in virtualisation
- +
Computerworld Live Podcast #96: Security at the Edge 11/06/2008 09:22:22
CW Live speaks with Amol Mitra, HP ProCurve Director of Marketing for Asia Pacific and Japan. Today's topic: how enterprises are starting to shift away from simply controlling security via server logins, firewalls and moving to more adaptive security frameworks. - +
Data Management Edition #10: Multi-Petascale Systems 02/05/2008 09:12:33
This week we look at sustainability and the development of multicore technologies to build multi-petascale systems. - +
IT Security Edition #11: How to poison the Storm botnet 01/05/2008 08:51:55
This week CW Live presents a case study on how to poison the notorious Storm botnet . Plus we take a look at Cisco's plans for Ironport. - +
IT Security Edition #10: Cyber-battles fought and won 24/04/2008 11:09:47
Vendors bow to end user pressure to improve product security, and we take a look at the latest concepts shaping the cyber-battlefield of the future. - +
Data Management Edition #9: Data centre makeover 24/04/2008 07:43:06
This week CW Live looks at the death of the old style data centre which is undergoing its first makeover in more than 30 years.
Satyam’s Q1 revenue up by 43% and Net Profit by 45% YoY; revises revenue and EPS guidance upwards for FY09 2008-07-18 16:58:00+10
Informatica Reports Record Second Quarter Results 2008-07-18 13:01:00+10
Tumbleweed Releases MailGate 3.6 2008-07-18 10:01:00+10
Convergys to Acquire Intervoice, Enhancing Leadership in Relationship Management 2008-07-17 14:41:00+10
Borland Management Solutions Put the "M" in Application Lifecycle Management 2008-07-17 13:43:00+10
Unified Communications: Justifications and Predictions
Building a business case for Unified Communications is currently more of an art than a science. However, the difficulty of building a business case for UC does not mean that there is none - just that we need to view (and measure) UC's benefits in accordance with the stage of maturity of the technology's adoption. Read on to find out more.











Comments
Flaw in testing Methodology?
While I don't pretend to be an expert - it seems to me that there is a flaw in the methodology for this test.
By definition, PSM is designed to save the battery drain during those periods where the radio is not needed for connection. By creating a continuous loop, with a standardised delay, the feature we are trying to test is actually being controlled.
In this test, EVERY delay between bursts was 3 seconds. In reality, this delay could be much longer, or much shorter. Setting a standardised sleep time is unrealistic, and the closer to 0 seconds the delay, the less the impact of PSM over CAM.
I would be interested to see if the results were replicated in a more realistic test scenario.