BenchmarkXPRT Blog banner

Category: HDXPRT 2012

HDXPRT 2012 characterization study

For HDXPRT 2011, we did quite a bit of testing to characterize the benchmark. Those results appeared in an initial white paper and a follow up one. In the first, we ran tests on different processors, various amounts of RAM, internal vs. external graphics, hard disk vs. SSD, and the effects of Intel Turbo Boost Technology. In the follow up white paper, we looked in more depth at the effect of graphics cards with different processors.

I mentioned a couple weeks ago that we are starting to put together a testbed to help us characterize HDXPRT 2012. What is in that testbed will define what characteristics of the upcoming benchmark we measure. We would like to get your help defining that testbed.

Our current thinking is to do a similar set of tests this year with updated hardware. However, plenty of additional things would be interesting to look at. First, I would like to increase the range of processors we test, including AMD processors. I would also like to do some testing varying different processor characteristics such as threads, cores, and frequency. It might also be good to look at the effect of new technologies like hybrid drives (which combine a small SSD with a hard disk to try and have the best of both).

We face two challenges in doing these characterization tests. One is to try and change one only variable at a time. That is very difficult in some cases, such as comparing Intel and AMD processors—you can’t just swap them in the same motherboard. Fortunately, it is usually possible to find very similar motherboards and keep other components (like disks, graphics, and RAM) constant. The other challenge is getting all of the necessary hardware in house.

So, we have two requests for you. First, let us know what you would like to see us test. Second, help us by supplying some of that equipment. If you supply the equipment we will do our best to include results from it in the characterization study and in the new HDXPRT 2012 results database. As always, thanks for your help!

Bill

Comment on this post in the forums

Change is inevitable

As we get close to the beta version of HDXPRT 2012, I wanted to let you know how it compares with the original design specification. As inevitably happens in any software project, there are differences between the original design and the final product. Generally, things have stayed pretty close with HDXPRT 2012, but there are two changes worth noting.

First, in the design specification, we specified Audacity 1.3.14 Beta in the Music Maker scenario as that was the only version that supported Windows 7 at the time. Audacity 2.0 with Windows 7 debuted in the interim so we are using that version.

The second and more significant issue was with Picasa, which was to be part of the Media Organizer scenario. Unfortunately, we couldn’t create a stable script because scripting tools like AutoIT could not properly recognize some of Picasa’s application UI elements. Somewhat reluctantly, we ended up replacing Picasa with Photoshop Elements. We still think the scenario is a good one and Photoshop Elements is an appropriate tool. I would have liked, however, to have Picasa in there.

There are probably some more minor differences between the beta and the design specification. We’ll let you know what they are when we have the beta ready in a couple weeks. (Hopefully!) We’re looking forward to getting that into your hands and getting your feedback. If you’re not already a member of the Development Community, I encourage you to join so that you can get your copy of the beta when it is available.

Bill

Comment on this post in the forums

HDXPRT 2012 – Testing the test

We’re currently starting testing on alpha versions of HDXPRT 2012. In order to do that, we’re putting together a testbed. We have two goals for the testbed that are somewhat contradictory. The first is to make the testbed as diverse as possible in terms of vendors and configurations. We want notebooks and desktops from as many vendors as possible. We want to make sure we have systems that will push the edges—both slower systems that may even be below the minimum recommended configuration and faster ones representing the current latest and greatest. These systems will help us shake out bugs and provide some raw data that we can publish when the benchmark debuts in the new results database.

The second goal for the testbed is to have systems where we can easily change one variable at a time to help us understand the characteristics of the benchmark. Typically, these are white box systems where we can swap processors, disks, RAM, and so on. We will use the results from these systems in the benchmark characterization white paper we will create for the debut of HDXPRT 2012.

We’d like your opinions on what we should be certain to test. We think we have a good handle on what to include, but we want your ideas as well.

We also are looking for additional systems to include in our testbed. If you can supply some, please let me know. That is one way to make sure HDXPRT 2012 works on your system and to get your results in the results database. Rest assured, we will not publish those results without your permission. Regardless, the more systems we can test, the better the final product will be.

There will, of course, be opportunities for you to help with the testing as we get to the beta stage in the near future.

Bill

Comment on this post in the forums

Bye, bye 32 bits?

In developing HDXPRT 2012, we have encountered a dilemma. The problem is the amount of effort necessary to support 32-bit as well as 64-bit. While the world is moving to 64-bit Windows, some older platforms as well as possibly some lower-end devices still use 32-bit Windows. Our feeling is that the effort necessary to support 32-bit Windows would be better spent elsewhere, such as working on TouchXPRT. Further, supporting 32-bit Windows might have a noticeable impact on when we can complete HDXPRT 2012.

The downside in supporting only 64-bit Windows is that we had hoped to be able to increase the range of devices HDXPRT 2012 supports. The advent of TouchXPRT, however, means that it might be the more appropriate benchmark for those lower-end devices that consume content rather than create it. What do you think? This is one decision where we would really like your input. So, should we support 32-bit Windows or limit HDXPRT to 64-bit? Thanks!

Bill

Comment on this post in the forums

Quick HDXPRT 2012 status update

Between talking about CES, the new touch benchmark, and sausage making, it seems like it’ has been a while since I’ve said anything about HDXPRT. Here’ is a quick status update. The short form is that folks are heads- down coding, debugging, and testing. We still have some significant hurdles to overcome, such as trying to script Picassa. We also are going to have to make some difficult decisions in the near future about possibly swapping out one or two of the applications due to either licensing or scripting issues. (Sausage making at its best!) We’ll keep you posted in the forums when we have to make those decisions.

There is still a lot to get done, but things still appear to be on schedule. That schedule means that we are still hoping to have a beta version available for the Development Community to test in late March. At that point, the beta version will be available to our members and we will really need your help to try and shake things out. (Join at http://hdxprt.com/forum/register.php if you are not yet a member of the Development Community and want to help in our effort.) The more different systems and configurations we can all test together, the better the benchmark will be. There will also be at least some time for feedback on whether HDXPRT 2012 matches the design specification and if there are any last- minute tweaks you think would help make for a better benchmark.

So, stay tuned! We look forward to continuing to work with you on making HDXPRT 2012 even better than the current version.

Bill

Comment on this post in the forums

A touch of tomorrow

As is often the case for me, Christmas shopping has given me the chance to look at all sorts of gadgets. (No, I’m not sure who to buy them for, but that isn’t the point.) The wealth of touch-based devices like the iPad, the Kindle Fire, the Galaxy Tab, and phones of all sorts is either incredibly exciting or amazingly confusing. Touch-based interfaces have moved well beyond the devices they started on and are showing up pretty much everywhere. Even my car (a Nissan Leaf) uses a touch interface. When I use a device with a screen, like my camera, and can’t touch the screen, it just feels wrong.

The power of computing devices like the iPad and other tablets is bringing touch into what we traditionally think of as the PC marketplace. The debut next year of Windows 8 with its touch-based Metro user interface will add another serious player to the mix. Touch will be in your desktop and notebook future. (Which for me means a steady supply of cloths for wiping screens will be a necessity, but that’s another story.) I think that touch will be the dominant interface—surpassing the mouse—in the near future.

When I see that kind of shift in the marketplace, and the resulting product diversity, my background makes me think that such an area is ripe for some good tools to compare the products. What do you think? Do we need a new generation of touch-based benchmarks for Metro? For other touch-based platforms?

Back here in HDXPRT Central, I do want to mention that the HDXPRT 2012 design specification is now available. Check it out at http://www.hdxprt.com/forum/2012_design_specification.php!

Bill

Comment on this post in the forums

Check out the other XPRTs:

Forgot your password?