BenchmarkXPRT Blog banner

Category: Chromebooks

Side by side

We’re making a big upgrade to the Spotlight: It will now let you make side-by-side comparisons of any of the devices we’ve featured. You’ll also be able to filter devices by type.

We’ve also added pricing information to the Spotlight. The price of a device can vary a lot, depending on the options you select. We give you the price we paid for the device as we tested it. Because prices can vary over time, we also give the date when we bought the device.

We think these changes will make the Spotlight an even more powerful tool for helping with buying decisions.

We also created a special page, the Back to School Roundup. It provides side-by-side comparisons of 13 of the hottest devices to help families and students choose the right ones for their educational needs. We include a range of device types—all-in-ones, Chromebooks, convertibles, laptops, and tablets—and operating systems—Chrome OS, OS X, and Windows.

Going forward, we’ll be adding more advanced querying features. Of course, we’ll also add new devices every week.

Check it out! And, if you have any ideas about how to make the XPRT Weekly Tech Spotlight more useful, let us know!

Eric

They’re coming!

We’ve been hearing for a while about Google’s plan to bring Android apps to Chrome.  They recently published a video on the Google Developers channel that gives us some idea of what running Android apps on a Chromebook would look like.

Because I’m very interested in performance, the claim “Android apps can run full speed, with no overhead and no performance penalties” got my attention. You can bet we’ll be using the XPRTs to check that out! We’re using a Google developer tool called ARC Welder to do some experiments. However, it’s not fair or valid to print performance results based on a developer tool, so we’ll have to wait until the official release to see what the performance is really like.

Obviously, the use cases for Chrome will be changing. The demos in the video are for workloads we associate with PCs. MobileXPRT-type workloads might be more appropriate, or, assuming the scripting tools are available, perhaps HDXPRT-type workloads. We’ll be watching these developments closely to see how they will affect our future cross-platform benchmark.

Eric

Ready for your closeup?

On January 6, we announced the XPRT Weekly Tech Spotlight. We spotlighted the first device, a Google Pixel C, on February 8. Since then, we’ve spotlighted around 20 devices, and the list keeps growing with phones, tablets, Chromebooks, and laptops. The XPRT Weekly Tech Spotlight has been a big success and is one of our most visited pages.

XPRT Spotlight 1

From the beginning, we’ve offered to spotlight your device for free, though we will need to keep the device to allow for retesting with future versions of the OS and benchmarks. Any device you contribute jumps to the head of the queue, and will be in the Spotlight the following week. We have a page for vendors with all the details.

XPRT Spotlight 2

As we continue to spotlight new devices, we are thinking about ways to allow you to compare their specs and XPRT results. We would love to hear your thoughts on what capabilities would be useful to you in those comparisons.

Looking forward to seeing your device in the spotlight soon!

Eric

A guest blog from Wilson Cheng at Acer Inc.

Two years ago, I got a job to evaluate cross-platform benchmarks for comparing Windows and Android.

Usually, Web-based benchmarks focus on only Java-script and HTML5 functionality. I found WebXPRT is easy to use and includes the tasks that you do every day. It reliably tests the user experience and gives a simple score for comparison. I suggested to our manager that we use it to evaluate our platform and he agreed.

Recently, Chromebooks have become very popular. Testing the battery life of Chromebooks has been difficult because you have needed to use the power_LoadTest image from the Chromium project or the test image from the Chrome OS Partners Web site to do power load testing. Without reimaging the system, you couldn’t test battery life. Because CrXPRT is designed to test battery life as well as performance on ChromeOS, this extra step is no longer needed. We can run CrXPRT without updating the test image, which is very useful in our battery life testing.

The advantage of XPRT benchmarks is that they are easy to use and give real-world results. The disadvantage is that they are not yet popular on review sites.

An updated CrXPRT 2015 build is available

Today we’re releasing a new build of CrXPRT 2015 (v1.0.2) in the Chrome Web Store. The updates included in this build correct the handling of outlier scores for individual workloads, check the duration of each battery-life test iteration, and introduce a check to ensure that the system is not plugged in during battery-life testing. The tests have not changed, and the method of calculating the overall score and battery-life score is the same, so the main scores are comparable with previous CrXPRT scores.

We published the update today in the Chrome Web Store as of 3:00 PM EST, but it may take some time for the update to appear on your system. You may have to manually approve the update notice when it appears on your system.

If you have any questions about the update or any other XPRT-related topic, feel free to contact us at BenchmarkXPRTsupport@principledtechnologies.com.

Polishing the chrome

Early next week, we’ll be releasing an update for CrXPRT that addresses a couple of issues. First, the individual workload scores were not always discarding outliers correctly, which could have had a small effect on those scores. The update handles outliers correctly. Because the overall score is calculated separately from the individual workload scores, this change does not affect the overall score or battery life score, and results from previous builds are still comparable.

The update also checks the duration for each battery life test iteration. This helps detect conditions that could invalidate the test, such as someone manually putting a test system to sleep.

Finally, the update checks between iterations to see if the Chromebook is plugged in during the test. If so, CrXPRT will report an error and stop the test. This can potentially save time that would otherwise be lost on an invalid run.

These are small changes, but they will help make CrXPRT a more robust benchmark.

In other news, we’ve been asking members of the community if they would care to share their experiences and thoughts on the blog.  We’re delighted that people are interested, and we’ve already received our first guest post that we’ll be publishing in the next couple of weeks. In the meantime, if you’d like to write a post, or just want to share your thoughts on the XPRTs, please let us know!

Eric

Check out the other XPRTs:

Forgot your password?