BenchmarkXPRT Blog banner

Category: WebXPRT

Mystery solved

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

Bit by bit

We’ve been working to internationalize the XPRTS. Our initial attempts have focused on China.

Both BatteryXPRT and WebXPRT have Chinese UI options. We expect to have a version of MobileXPRT with a Chinese UI option available in a couple of weeks.

We’ve also been working to make the benchmarks more accessible in China. WebXPRT has a mirror host site in Singapore. We’re also getting the XPRTs into Chinese app stores. MobileXPRT is available in two Chinese app stores: Xiaomi (http://app.mi.com/detail/90862) and Zhushou 360 (http://zhushou.360.cn/detail/index/soft_id/2984653). We aim to have BatteryXPRT and the Chinese version of MobileXPRT available in those stores as quickly as possible.

Obviously, we will continue to work to improve our localization. This is an area where we can use the help of the community. If you have the translation skills and want to contribute the strings for a UI for your language, let us know.

Eric

Rolling with the changes

While WebXPRT 2015 has been running fine on earlier beta versions of Windows 10, we have found a problem on some recent versions. Starting with build 10122, the Local Notes test hangs when using the Microsoft Edge browser. (Note: This browser still identifies itself as Spartan in the builds we have seen.) Chrome and Firefox on Windows 10 have successfully run WebXPRT 2015, so the problem appears to be restricted to Edge/Spartan.

Because WebXPRT ran successfully on earlier builds of Windows 10, we are hoping that upcoming builds will resolve the problem. However, we have been investigating the issue in case there is something we can address. The problem is that the encrypted strings that the test is trying to write to LocalStorage are not being written correctly. Non-encrypted strings are being written correctly.

As soon as the problem gets resolved, we’ll let you know.

In other news, we’ve been looking at Android M. There are a lot of interesting changes coming, such as the difference in the way that Android M manages app permissions. We’ve decided to delay releasing the design document for the next version of MobileXPRT so that we can make sure that the design deals with these changes appropriately.

Eric

It’s not the same

We sometimes get questions about comparing results from older versions of benchmarks to the current version. Unfortunately, it’s never safe to compare the results from different versions of benchmarks. This principle has been around much longer than the XPRTs. A major update will use different workloads and test data, and will probably be built with updated or different tools.

To avoid confusion, we rescale the results every time we release a new version of an existing benchmark. By making the results significantly different, we hope to reduce the likelihood that results from two different versions will get mixed together.

As an example, we scaled the results from WebXPRT 2015 to be significantly lower than those from WebXPRT 2013. Here are some scores from the published results for WebXPRT 2013 and WebXPRT 2015.

WebXPRT 2013 vs. 2015 results

Please note that the results above are not necessarily from the same device configurations, and are meant only to illustrate the difference in results between the two versions of WebXPRT.

If you have any questions, please let us know.

Eric

WebXPRT 2015 source code is now available

As of today, we are making the WebXPRT 2015 source code available to community members.

Download the WebXPRT 2015 source here (login required).

We’ll also post a link to the source on the WebXPRT tab in the Members Area. The source code package contains instructions for setting up a local installation of WebXPRT. However, please note that you must test using WebXPRT.com to get an official result.

If you want more information, please contact BenchmarkXPRTSupport@principledtechnologies.com.

We look forward to your feedback!

WebXPRT 2015 is here!

Today, we’re releasing WebXPRT 2015, our benchmark for evaluating the performance of Web-enabled devices. The BenchmarkXPRT Development Community has been using a community preview for several weeks, but now that we’ve released the benchmark, anyone can run WebXPRT and publish results.

Run WebXPRT 2015

WebXPRT 2013 is still available here while people transition to WebXPRT 2015. We will provide plenty of notice before discontinuing WebXPRT 2013.

After trying out WebXPRT, please send your comments to BenchmarkXPRTsupport@principledtechnologies.com.

Check out the other XPRTs:

Forgot your password?