Month: June 2014

The updated BatteryXPRT is here

on June 30, 2014

As we mentioned a couple of weeks ago, we discovered stability issues when running BatteryXPRT 2014 for Android on devices with only 1 GB of RAM. We now have a build that’s stable on those devices. Battery life and performance results from the new build are equivalent to those from the previous build, so your existing results are still valid and comparable.

You can download the new build of BatteryXPRT 2014 for Android at BatteryXPRT.com or through the Google Play Store. If you have any questions, please don’t hesitate to ask.

Eric

Comment on this post in the forums

In the works

By Eric Hale

on June 26, 2014

A couple of weeks ago, we mentioned stability issues with BatteryXPRT 2014 for Android when running on systems with only 1 GB of RAM. After some restructuring, we now have a build that’s stable on those devices. We’re finishing testing, and it’s looking good. We’ll be making the new build available at BatteryXPRT.com and in the Google Play store early next week. Battery life and performance results from the new build are equivalent to those from the previous build, so your existing results are still valid and comparable.

Speaking of BatteryXPRT, we have something special coming soon. I can’t say what it is yet, but we haven’t done anything like it before.

We’re also getting closer to a general release for HDXPRT 2014. As we’ve explained before, the new HDXPRT runs three iterations in less than 2 hours, and will be downloadable, so the entire installation and testing process is much quicker than before. We’re currently working out a few kinks, but we expect the general release very soon.

Also, we’re still accepting ideas for naming the Chrome-related XPRT now in development. Share your ideas at BenchmarkXPRTsupport@principledtechnologies.com.

Eric

Comment on this post in the forums

Posted in BatteryXPRT 2014 for Android, Chrome OS, Collaborative benchmark development, HDXPRT 2014 |

Testing the waters

By Eric Hale

on June 19, 2014

A couple of weeks ago, we talked about some of our ideas for a new XPRT designed for Google’s Chrome OS. We’ve been working with some of these ideas and, while we’re still in the experimental stage, things look promising so far.

As we mentioned in the earlier blog, we’re trying WebXPRT as a base for the performance part of the test. So far, the performance component is working well. In addition to modified WebXPRT tests, we’re also trying some things that are not part of the WebXPRT 2013 workload.

We’ve been able to get battery life, but it’s been challenging and we haven’t found a way to avoid using Chrome’s Developer Mode. Accessing Developer Mode in Chrome can be tricky and requires different steps for each hardware manufacturer. We’re hoping to find ways to make battery life testing easier.

I’ve been vague about the tests because they’re likely to change over the next few weeks. We’re experimenting with both browser-based and Native Client-based performance tasks. As they firm up, I’ll be able to share more information.

Challenges aside, we’re excited about this new benchmark, and committed to making it as effective as possible. We’d still love feedback on a name, so feel free to contact us at BenchmarkXPRTsupport@principledtechnologies.com with your ideas.

Eric

Comment on this post in the forums

Posted in Battery life, Chrome OS, Collaborative benchmark development, Performance benchmarking, What makes a good benchmark? |

A new version of BatteryXPRT is coming

By admin

on June 12, 2014

We’ve found that BatteryXPRT 2014 for Android has some stability issues on some devices with low memory. We’ve investigated the problem and found that the problem is that the low RAM reduces the per-application heap quota so much that BatteryXPRT may not run correctly.

To address this problem, we’ve restructured BatteryXPRT so that it stays within the heap limits on devices with 1 GB of RAM. We are currently testing the restructured version of BatteryXPRT and it looks good so far. It takes a while to thoroughly test BatteryXPRT, but we will release the new build as soon as we complete testing it.

We haven’t seen any change in the performance or battery life results in the testing so far. You’ll be able to safely compare your existing results with the results from the rebuilt version.

Remember that we are looking for ideas, and a really great name, for a Chrome OS benchmark. If you have any ideas, or are curious about the changes to BatteryXPRT , let us know!

Eric

Posted in Android, BatteryXPRT 2014 for Android |

The name game

By Eric Hale

on June 5, 2014

In Something shiny, we discussed the leading contender in our search for new benchmark ideas, a benchmark tailored especially for the Chrome OS, and we’ve been looking at what workloads would make sense.

As we said, the ability to measure battery life would be useful. That’s not easy in the Chrome environment. We think we may be able to do it, but the Chromebook may have to be in developer mode. Even so, we can leverage what we’ve learned from BatteryXPRT to get a reliable estimate of battery life in less than a working day.

Measuring performance, however, is a must. We’ve been looking at the existing WebXPRT workloads as well as other applications, such as education apps, online games, HD video playback, music playback, and more. We’re also looking for areas where using native client execution makes sense, such as higher-resolution photo editing.

In addition, we’re thinking about what we might call this benchmark. ChromeXPRT would be obvious, but probably wouldn’t pass Google’s naming restrictions.

Do you have ideas for the benchmark’s name? Are there Chrome-based benchmark workloads you’d love to see? Let us know at BenchmarkXPRTsupport@principledtechnologies.com!

Eric

Comment on this post in the forums

Posted in Chrome OS, Collaborative benchmark development, Future of performance evaluation, WebXPRT |

Month: June 2014

The updated BatteryXPRT is here

In the works

Testing the waters

A new version of BatteryXPRT is coming

The name game

Check out the other XPRTs: