Latest software headlines from Network World:
File storage and viewing apps for iPhone
|
Does Verizon's Voyager stack up to the iPhone? |
|
|
5 IT skills that won't boost your salary
[1,407]
Women 4 times more likely than men to cough up personal info
[589]
Japan's 10 funniest tech-related commercials [Videos]
[407]
Throwing away a promo CD is "unauthorized distribution"?
[1,265]
Adults too quick to dismiss educational video games
[682]
Attack of the iPhone clones [Slideshow]
[578]
10 things IT needs to know about AJAX
[1,258]
This Year's 25 Geekiest 25th Anniversaries [Slideshow]
[409]
|
|
Not flawed, but maybe not the whole story
Craig,
I agree that the test was not flawed. However, did you test different combinations of beacon interval and/or DTIM settings on the access point? If so, you might see your results improve (or worsen).
One of the main problems with 802.11 PSM is that it is statically set at the AP for all clients. It has been shown that, as you observed, PSM can have little effect, or even cause higher power consumption, depending on traffic patterns, the round-trip time of TCP traversals, and how packets "line up" in time with the beacon/DTIM intervals. Since the client has no ability to vary its individual power save profile settings, it is at the mercy of the AP settings as to what effect PSM has.
You are correct that in a laptop scenario, the WLAN power savings due to PSM are most likely relatively minor compared to the other subsytems' consumption. In an application such as wireless sensors, though, where the WLAN radio is usually the major system power draw, communications can be infrequent, and one has to deal with a very limited power budget, we have seen that properly tuned PSM settings can significantly reduce the average power consumption of the overall solution. Again, however, the same settings that minimize one client's consumption can have the exact opposite effect on another client.
Thanks. -Michael Blossom