BenchmarkXPRT Blog banner

Category: Source code

Reflecting on 2016

The beginning of a new year is a good time to look back on the previous 12 months and take stock of everything that happened. Here’s a quick recap of a very busy year:

In 2016, the XPRTs travelled quite a bit. Eric went to CES in Las Vegas, Mark attended MWC in Barcelona, and Bill flew out to IDF16 in Shenzhen.

We also sent a team to Seattle for the first XPRT Women Code-A-Thon, an event we’re very proud to have sponsored and co-hosted along with ChickTech, a nonprofit organization dedicated to increasing the number of women in tech-related fields. The Code-a-thon also served as inspiration for an eight-part video series entitled Women Coding for Change. The series explains the motivation behind the Code-a-thon and profiles several of the participants. If you haven’t watched the videos, check them out. They’re well worth the time.

Speaking of videos, we also published one about Nebula Wolf, the mini-game workload produced through our first collaboration with the North Carolina State Senior Design Center. That experience was promising enough for us to partner with another student team this past fall, which resulted in a virtual reality app that we hope to share with the community in the near future.

Of course, we also continued work on our suite of benchmark tools and related resources. We released TouchXPRT 2016 to the public, published the Exploring TouchXPRT 2016 white paper, and released the TouchXPRT 2016 source code to community members.

In 2016, we unveiled the XPRT Weekly Tech Spotlight, a new way for device vendors and manufacturers to share verified test results with buyers around the world. We put 46 devices in the spotlight throughout the year and published Back-to-School, Black Friday, and Holiday device showcases.

In the last quarter of 2016, we celebrated our most widely-used benchmark, WebXPRT, passing the 100,000-run milestone. WebXPRT is still going strong and is as useful and relevant as ever!

Finally, we ended the year with the exciting news that we’re moving forward with efforts to develop a machine-learning performance evaluation tool. We look forward to engaging with the community in the coming year as we tackle this challenge!

As always, we’re grateful for everyone who’s helped to make the BenchmarkXPRT Development Community a strong, vibrant, and relevant resource for people all around the world. Here’s to a great 2017!


MobileXPRT 2015 source code and TouchXPRT 2016 Design Overview are available

We’re excited to announce that the MobileXPRT 2015 source code and TouchXPRT 2016 Design Overview are now available to community members!

Download the MobileXPRT 2015 source here (login required).

Download the MobileXPRT 2015 build instructions here (login required).

Download the TouchXPRT 2016 Design Overview here (login required).

We also posted links to all three items on the MobileXPRT and TouchXPRT tabs in the Members’ Area.

If you want more information, please contact

We look forward to your feedback!

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 to get an official result.

If you want more information, please contact

We look forward to your feedback!

HDXPRT 2014 source code is now available

As mentioned in the XPRT blog, we are making the source code available to community members.

Download the HDXPRT 2014 source here.

We’re also posting HDXPRT build instructions in the Members Area. If you want more information, please contact

We look forward to your feedback!


Comment on this post in the forums

HDXPRT 2014 source code coming soon

We’ve really been enjoying the smaller size and quicker install and runtimes of HDXPRT 2014, and we encourage you to give the benchmark a try if you haven’t already! Within the next week or so, we’ll make the HDXPRT 2014 source code available to BenchmarkXPRT Development Community members. Part of what makes the XPRT community work is the feedback we get from members, whether it comes in the form of new benchmark ideas, suggestions for improvement, or questions raised during community preview testing. Having members comb through the code is another aspect of that community model. We welcome any members with programming skills to comment on our code and submit their own code for review.

If you decide to submit code, please read the XPRT commenting conventions, which are simply brief descriptions of a few practices that will make it easier for us to read your code.

We’ll also post detailed build instructions for HDXPRT 2014 in the Members Area. When the source code is available, check it out and let us know what you think. If you have code to share, please post on the forums or send us a message. If you haven’t yet joined the community, we’d love for you to join now.


Comment on this post in the forums

Looking for a bargain?

There are many benefits to being a member of the community: the XPRT community previews, the source code for the benchmarks, the monthly newsletter, and more. To join the community, all you’ve had to do up until now is sign up and pay a one-time $20 fee. Our goal with the fee was to make sure that people who joined were serious.

Today, we’re announcing a change. We recognize that, for some companies, getting that $20 fee reimbursed can be a hassle. So, if you work for a device maker, OEM, chip manufacturer, or retailer, you’ll be able to join the community for free.

Here’s how it works: Simply fill out the form, use your company e-mail address, and click the option to be considered for a free membership. We’ll send you an email within one business day to verify the address is real and then activate your membership.

Simple, right?


Comment on this post in the forums

Check out the other XPRTs:

Forgot your password?