Category: Uncategorized

Each new XPRT benchmark release attracts new visitors to our site. Those who haven’t yet run any of our benchmarks may not know how everything works. For those folks, as well as longtime testers who may not be aware of everything the XPRTs have to offer, we like to occasionally revisit the basics here in the blog. Today, we cover the simple process of submitting WebXPRT 4 test results for publication in the WebXPRT 4 results viewer.

Unlike sites that publish all results that users submit, we publish only results—from internal lab testing, user submissions, and reliable tech media sources—that meet our evaluation criteria. Scores must be consistent with general expectations and, for sources outside of our lab, must include enough detailed system information that we can determine whether the score makes sense. Every score in the WebXPRT results viewer and on the general XPRT results page meets these criteria.

Everyone who runs a WebXPRT 4 test is welcome to submit scores for us to consider for publication. The process is quick and easy. At the end of the WebXPRT test run, click the Submit your results button below the overall score, complete the short submission form, and click Submit again. Please be as specific as possible when filling in the system information fields. Detailed device information helps us assess whether individual scores represent valid test runs. The screenshot below shows how the form would look if I submitted a score at the end of a WebXPRT 4 run on my personal system.

After you submit your score, we’ll contact you to confirm how we should display the source. You can choose one of the following:

• Your first and last name
• “Independent tester” (for those who wish to remain anonymous)
• Your company’s name, provided that you have permission to submit the result in their name. If you want to use a company name, please provide a valid company email address.

We will not publish any additional information about you or your company without your permission.

We look forward to seeing your score submissions. If you have suggestions for the WebXPRT 4 results viewer or any other aspect of the XPRTs, let us know!

Justin

Yesterday, we published the WebXPRT 3 release notes, which contain instructions on how to run the benchmark, submit results, and use automation to run the tests.

Test automation is a helpful feature that lets you use scripts to run WebXPRT 3 and to control specific test parameters. Below, you’ll find a description of those parameters and instructions for utilizing automation.

Test type

The WebXPRT automation framework is designed to account for two test types: the six core workloads and any experimental workloads we might add in future builds. There are currently no experimental tests in WebXPRT 3, so the test type variable should always be set to 1.

• Core tests: 1
• Experimental tests: 2

 
Test scenario

This parameter lets you specify which tests to run by using the following codes:

• Photo enhancement: 1
• Organize album using AI: 2
• Stock option pricing: 4
• Encrypt notes and OCR scan: 8
• Sales graphs: 16
• Online homework: 32

 
To run an individual test, use its code. To run multiple tests, use the sum of their codes. For example, to run Stocks (4) and Notes (8), use the sum of 12. To run all core tests, use 63, the sum of all the individual test codes (1 + 2 + 4 + 8 + 16 + 32 = 63).

Results format

This parameter lets you select the format of the results:

• Display the result as an HTML table: 1
• Display the result as XML: 2
• Display the result as CSV: 3
• Download the result as CSV: 4

 
To use the automation feature, start with the URL http://www.principledtechnologies.com/benchmarkxprt/webxprt/2018/3_v5/, append a question mark (?), and add the parameters and values separated by ampersands (&). For example, to run all the core tests and download the results, you would use the following URL: http://principledtechnologies.com/benchmarkxprt/webxprt/2018/3_v5/auto.php?testtype=1&tests=63&result=4

We hope WebXPRT’s automation features will make testing easier for you. If you have any questions about WebXPRT or the automation process, please feel free to ask!

Justin

At the beginning of each new year, we like to look back on the previous 12 months and review everything that we accomplished. Here’s a quick recap of an eventful 2017 for the XPRTs:

We continued our tradition of travelling to the world’s biggest tech expos. Bill went to CES in Las Vegas and MWC Shanghai, and Mark attended MWC in Barcelona. Travelling to these shows provides us with great opportunities to monitor industry trends and meet with other BenchmarkXPRT Development Community members.

We also continued work on our suite of benchmark tools and related resources. We updated BatteryXPRT in response to changes in the Android development environment, released two new HDXPRT builds to make installation and test configuration easier on new Windows 10 builds, and released the much-anticipated WebXPRT 3 Community Preview.

We released new media, including a video about our sponsorship of a team of North Carolina State University students who created an experimental VR demo workload, and new interactive tools, such as the XPRT Selector tool and the WebXPRT Processor Comparison Chart.

We continued to improve the XPRT Weekly Tech Spotlight by adding more devices, photos, and site features. We put 51 devices in the spotlight throughout the year and published updated back-to-school, Black Friday, and holiday showcases to help buyers compare devices.

At the end of the year, our most popular benchmark, WebXPRT, passed the 200,000-run milestone. WebXPRT use continues to grow around the world, and it has truly become an industry-standard performance benchmark for OEM labs, vendors, and leading tech press outlets.

We also continued work on our most challenging project to date, a benchmark for machine learning. We look forward to sharing more information on that effort with the community over the next few months.

We’re thankful for everyone who used the XPRTs, joined the community, and sent in questions and suggestions throughout 2017. Each one of you helped to make the BenchmarkXPRT Development Community a strong, vibrant, and relevant resource for people all around the world. Here’s to a great 2018!

Justin