BenchmarkXPRT Blog banner

Category: WebXPRT

News about MobileXPRT 2013 and WebXPRT 2015

Today, we’re releasing a new build (v92) of MobileXPRT 2013 at MobileXPRT.com and the Google Play store. This build addresses issues encountered when testing MobileXPRT on Android 5 devices. The tests have not changed, so new scores are comparable with previous MobileXPRT 2013 scores.

Click here to download the new MobileXPRT build directly from our site.

Alternatively, you can download the MobileXPRT 2013 APKs directly. The APKs are small (17.9 MB total) and allow you to download the test content during installation. For users who have trouble accessing the Google Play store, these APKs may make it easier to download the benchmark.

Download the MobileXPRT APK here.
Download the MobileXPRT UX Tests APK here.

Also, today we’re publishing the WebXPRT 2015 Design Overview document for community members. You can find the document on the WebXPRT tab in the Members’ Area. We look forward to your feedback!

If you have any questions or concerns about these or any other XPRT-related topics, feel free to contact us at BenchmarkXPRTsupport@principledtechnologies.com.

Comment on this post in the forums

The value of diversity

It’s great to hear from community members who are using the XPRTs. Having a pool of users with diverse viewpoints is critical for successful software development. While we try very hard to find problems, there will always be cases we miss.

For example, we talked recently about the challenges of working in a multilingual world. Just this week, Acer reported an interesting bug in the CrXPRT community preview. If your language is set to Chinese, the battery test will estimate the battery life as expected. However, a rundown test will return the message “Cannot calculate total run time.” This does not happen when the language is set to English.

We have verified this problem. In the next week or so, we’ll be releasing a second community preview containing a fix for this and a few other issues.

We’ve talked before about the difficulties of maintaining software in a fast moving world. Late last week, we received a new Nexus 9. It encountered a problem during the MobileXPRT tests, so we fixed the problem and will be releasing a patched build tomorrow.

Don’t forget, as we said last week, we’ll be releasing the WebXPRT 2015 design overview tomorrow. We are looking forward to the feedback from all our community members.

Eric

Comment on this post in the forums

Upcoming experiments

Next week, we’ll be releasing the design overview for WebXPRT 2015. WebXPRT 2013 has been an enormous success, having been run tens of thousands of times.

One of the big improvements we are considering for WebXPRT 2015 is adding experimental tests. A big reason for WebXPRT’s success is that it runs on almost every Web-enabled device. We consider it essential to preserve this broad compatibility. However, there are interesting Web technologies that simply are not available on all devices.

Our proposal is to add experimental tests to WebXPRT. These tests would be optional and would not be included in the Overall score, so WebXPRT would still be able to compare the performance of widely different devices. We are looking at technologies such as Web Workers, WebGL, and pre-compiled JavaScript (asm.js).

In addition to adding experimental tests, we are looking at ways to improve the UI, add automation, add new tests, update old tests, and more!

If you are a community member, you’ll get a notice when the overview is available. We will definitely want to know what you think! If you are not a member, it’s a great time to join.

If you have any thoughts on these ideas, or have ideas of your own, please let us know!

Eric

Comment on this post in the forums

Time to get creative

The CrXPRT Community Preview is right around the corner, and there’s no sign of things slowing down. We’re exploring new opportunities on a number of fronts, and we’d love to hear what you think! We’re considering possible changes to WebXPRT and MobileXPRT, and since the mobile device market is changing all the time, we’re looking for the next great benchmark opportunity. In both cases, the development community is a rich source of ideas, so we’d like to tap into it one more time.

A while back, we added a new Web form in the members’ area for submitting benchmark ideas. Some of the ideas we have so far include:

  • A benchmark to evaluate camera features and photo quality on phones and tablets
  • A benchmark for measuring the performance of cloud services
  • A benchmark for measuring the performance and battery life of iOS-based devices

So, what would you like to see? Any of these, or do you have ideas we haven’t mentioned? Also, we’d love to hear your feedback on ways we can improve, both with the XPRTs themselves and with community life. Either way, send a message to BenchmarkXPRTSupport@principledtechnologies.com and let us know what you think!

Justin

Comment on this post in the forums

More details to come

As we’ve been saying the past couple of months, we’re working on a benchmark for Chrome OS. The experimentation phase is winding down, and we are starting to shape the code into a useable benchmark. The design plan will leverage existing WebXPRT tests, of course. However, we’ve gone far beyond that. The benchmark will include video playback, 3D modeling via WebGL, and even an HTML5 game.  The test also uses Chrome OS’ native execution capability. The benchmark will actually use the Portable Native Client (PNaCl), as PNaCl is the recommended tool chain for native client. It also gives the benchmark the ability to run on more platforms.

As we mentioned before, we’re including a battery test as part of the new benchmark. So far, we haven’t found a way to remove the requirement to put the device in developer mode for the battery test.

Next week, we’ll publish a design document for the community to review. As always, the design document is based on the comments and suggestions we received combined with our own research and experimentation.

Eric

Comment on this post in the forums

It makes a difference

Ars Technica reported this week that they tested the developer preview of Android L and saw a whopping 36 percent improvement in battery life! Google made improving battery life a priority, and it sounds like they are succeeding. I can’t wait to test Android L with BatteryXPRT.

This is a spectacular example of how a change in software can change benchmark results, but it’s hardly unique. I’ve written before about how background activity on a phone depressed my friend’s WebXPRT scores. AnandTech used both IE 11 and Chrome 30 to test the Surface Pro 2 with a variety of benchmarks, including WebXPRT, SunSpider, Octane, Browsermark, and others. Browser choice had a noticeable impact on results – about a 40 percent difference for WebXPRT and a 76 percent difference for SunSpider!

People are generally pretty aware that changing the hardware changes performance. However, sometimes they lose track of software differences. When you compare scores, it’s not always possible to keep all the variables the same, but it’s crucial to know what the differences are.

In other BenchmarkXPRT news, we’re making some final adjustments to HDXPRT 2014, and the general release is just around the corner.

Eric

Comment on this post in the forums

Check out the other XPRTs:

Forgot your password?