Why Run Jetstress?

Jetstress 2010 is a tool provided by Microsoft for evaluating Exchange 2010 storage subsystem’s performance, scalability and reliability in lab environment. Jetstress 2010 works with the Microsoft Exchange Server 2010 database engine and simulates the Exchange’s IO workload accurately.

There are many reasons people run Jetstress in various situations. Below are four common usage scenarios. 

  • POC (Proof Of Concept). This is often done at the pre-sale stage. Customers or potential customers try out the storage systems and see how they behave under the workload generated by Jetstress. This is sort of kicking the tires. If the Jetstress test passes with flashy colors, that certainly leaves a good impression, even though it may not guarantee a sale. On the other hand, if the Jetstress test fails, then a deeper analysis would be followed. Obviously, that could slow down the sales process.
  • Design validation. This is usually carried out prior to the deployment of the Exchange solutions to production environment. Say the solution is carefully architected; proper sizing and capacity planning processes are followed. Before rolling out the solution to real world, Jetstress is run one more time to validate the design of the solution.
  • Product evaluation. When IT consulting firms (such as Enterprise Strategy Group and LionBridge) evaluate new products, often times they conduct their own tests by using various industry standard tools to generate workloads. To test Exchange storage subsystems, Jetstress is commonly used. Passing the Jetstress test is a pre-requisite of getting a good write-up.
  • ESRP (Exchange Storage Reviewed Program). ESRP is a Microsoft Exchange Server program designed to facilitate storage vendors testing and publishing solutions for Exchange. Jetstress is the testing harness inside ESRP. For a solution to be posted on Microsoft’s ESRP website, it must pass a set of Jetstress tests and pass Microsoft’s solution review process.

What about LoadGen? When talking about Jetstress, it’s very natural for us to think about LoadGen and wonder about the differences or similarities between the two. I have a blog post to discuss this very topic. It can be found here: https://communities.netapp.com/community/netapp-blogs/pseudo_benchmark/blog/2011/08/10/jetstress-loadgen.

Thanks for reading.