BenchmarkXPRT Blog banner

Category: Performance benchmarking

TouchXPRT 2016 Community Preview 3 is available

Eric Hale
By Eric Hale
on January 28, 2016

Today we are releasing TouchXPRT 2016 Community Preview 3 (CP 3). As we discussed in the blog, CP 3 resolves an issue reported on some systems, where the Create Slideshow test would take longer than expected to complete due to the output video not rendering correctly.

As with all community previews, TouchXPRT 2016 CP 3 is available only to community members. Members may download the preview from the TouchXPRT tab in the Members’ Area.

For more details about TouchXPRT 2016, please consult the release notes for further details (login required).

After you try out CP 3, please send us your comments. Either post them to the forum or mail them to BenchmarkXPRTsupport@principledtechnologies.com. If you send us information that’s relevant to the entire community, we may post an anonymous version of your comments to the forum.

Thanks for your participation!

Posted in BenchmarkXPRT development community, Collaborative benchmark development, Community Preview, Performance benchmarking, TouchXPRT, TouchXPRT 2016, TouchXPRT development process, TouchXPRT release cycle, Windows 10 |

TouchXPRT 2016 Community Preview 2 is available

Eric Hale
By Eric Hale
on December 1, 2015

Today we are releasing TouchXPRT 2016 Community Preview 2 (CP 2). As we discussed in the blog, some systems with newer AMD graphics drivers have trouble rendering the Create Slideshow from Photos output video. CP 2 includes a validation feature that produces an error when this problem occurs. This is the only change from the first community preview.

As with all community previews, TouchXPRT 2016 CP 2 is available only to community members. Members may download the preview from the TouchXPRT tab in the Members’ Area.

For more details about TouchXPRT 2016, please consult the release notes for further details (login required).

After you try out CP 2, please send us your comments. Either post them to the forum or mail them to BenchmarkXPRTsupport@principledtechnologies.com. If you send us information that’s relevant to the entire community, we may post an anonymous version of your comments to the forum.

Thanks for your participation!

Posted in BenchmarkXPRT development community, Community Preview, Performance benchmarking, TouchXPRT, TouchXPRT 2016, TouchXPRT development process, Windows 10 |

Question we get a lot

Eric Hale
By Eric Hale
on October 2, 2015

“How come your benchmark ranks devices differently than [insert other benchmark here]?” It’s a fair question, and the reason is that each benchmark has its own emphasis and tests different things. When you think about it, it would be unusual if all benchmarks did agree.

To illustrate the phenomenon, consider this excerpt from a recent browser shootout in VentureBeat:

 
While this looks very confusing, the simple explanation is that the different benchmarks are testing different things. To begin with, SunSpider, Octane, JetStream, PeaceKeeper, and Kraken all measure JavaScript performance. Oort Online measures WebGL performance. WebXPRT measures both JavaScript and HTML 5 performance. HTML5Test measures HTML5 compliance.

Even with benchmarks that test the same aspect of browser performance, the tests differ. Kraken and SunSpider both test the speed of JavaScript math, string, and graphics operations in isolation, but run different sets of tests to do so. PeaceKeeper profiles the JavaScript from sites such as YouTube and FaceBook.

WebXPRT, like the other XPRTs, uses scenarios that model the types of work people do with their devices.

It’s no surprise that the order changes depending on which aspect of the Web experience you emphasize, in much the same way that the most fuel-efficient cars might not be the ones with the best acceleration.

This is a bigger topic than we can deal with in a single blog post, and we’ll examine it more in the future.

Eric

Posted in Benchmark metrics, Benchmarking, Benchmarking computing devices, BenchmarkXPRT development community, Collaborative benchmark development, Performance benchmarking, Performance of computing devices, WebXPRT, What makes a good benchmark? |

MobileXPRT 2015 is here!

Eric Hale
By Eric Hale
on August 28, 2015

Today, we’re releasing MobileXPRT 2015, the latest version of our tool for evaluating the performance of Android devices. The BenchmarkXPRT Development Community has been using a community preview for several weeks, but now anyone can run MobileXPRT and publish their results.

MobileXPRT 2015 is compatible with systems running Android 4.4 and above. It is a 64-bit app, but will work on both 32-bit and 64-bit hardware. The new release includes the same performance workloads as MobileXPRT 2013, but not the UX Tests. If you need the UX tests, MobileXPRT 2013 will continue to be available here.

MobileXPRT 2015 is available at MobileXPRT.com and on the Google Play store. Alternatively, you can download the app using either of the links below:

 

After trying out MobileXPRT 2015, please submit your scores here and send any comments to BenchmarkXPRTsupport@principledtechnologies.com.  We’re eager to hear and see how you’ll use this tool!

Posted in Android, BenchmarkXPRT development community, MobileXPRT, MobileXPRT 2015, Performance benchmarking, Performance testing on tablets |

Mystery solved

Eric Hale
By Eric Hale
on July 2, 2015

As we mentioned a few weeks ago, the WebXPRT Local Notes test would not complete on recent builds of Windows 10 when using the Edge browser. Other browsers complete WebXPRT in recent Windows 10 builds without any problems.

We now know what is causing this behavior. The Local Notes test stores encrypted content in LocalStorage as UTF-16 character encoded Unicode strings. The encrypted content included values that are not considered valid characters in certain use cases.  The current Edge implementation treats these characters as undefined and cannot store them. Other browsers may not have had an issue with the characters because of differences in the way they implement LocalStorage.

We’ve been able to work around this by using escape sequences for unsupported Unicode code points.  Testing so far has not shown any perceptible change in results, so we believe that we will able to make this change to WebXPRT without compromising the comparability of the results.

Because this issue affects both WebXPRT 2013 and WebXPRT 2015, we’re planning to update both versions. We’ll let you know as soon as they are available.

If you’d like more details about this issue and the fix, please let us know.

Eric

Posted in Performance benchmarking, WebXPRT, WebXPRT 2015, What makes a good benchmark?, Windows 10 |

Hoping for a perfect 10

Eric Hale
By Eric Hale
on June 18, 2015

As many of you know by now, the release date for Windows 10 is July 29. As we’ve said before, we are hard at work getting TouchXPRT ready for Windows 10. We’ve succeeded in building TouchXPRT as a universal app, and it’s now running on Windows 10. We haven’t successfully run it on Windows 10 Phone yet, but we’re working on that.

Unfortunately, I can’t share any performance data. The EULA for the current build of Windows 10 (build 10143 as I’m writing this) forbids publishing benchmark results without prior written approval from Microsoft.

We’ll continue testing and refining the porting of TouchXPRT to Windows 10. Our goal is to release it as a universal app to the community in July.

What are your experiences testing Windows 10?  We’d love to hear about them!

Eric

Posted in Performance benchmarking, TouchXPRT, TouchXPRT development process, TouchXPRT release cycle, Windows 10 |

Check out the other XPRTs:

Forgot your password?
© Principled Technologies, Inc. 2025   |   Privacy policy

Cookie Notice: Our website uses cookies to deliver a smooth experience by storing logins and saving user information. By continuing to use our site, you agree with our usage of cookies as our privacy policy outlines.

x