Jet Stress 2013 – First Look!

Another day…. another tool. So. Jet Stress 2013. Microsoft has released it for download here. According to Microsoft in Technet “Jetstress 2013 works with the Microsoft Exchange Server 2013 database engine to simulate the Exchange database and log disk input/output (I/O) load.” While other third party SAN/disk vendors like to use other tools like IOMeter to check their performance, Jetstress concentrates specifically on how Exchange would behave on your current storage setup. This is important if you want to know if you storage is up to snuff for your future Exchange installation. With Jetstress 2013, Microsoft has continued this tradition of testing tools and extended it to Exchange 2013.

Installation

  • Simply download the tool from here.
  • Then run the Jetstress.msi to install the tool:

js2013-01
Click Next.

js2013-02
Click ‘I accept’ and then Next.

js2013-03
Either leave the defaults or enter a directory you want to install the tool to. Click Next.

js2013-04
Click Next.

js2013-05
Wait for the install to finish and then click Close.

Usage
Find the Jetstress 2013 icon on the Desktop.
js2013-06
Run the tool from here.

js2013-07
Once the tool is open, you will notice that there is a ‘Jetstress Help’ open in the lower left and this gives us a strange window:

js2013-08
It appears Microsoft has not quite yet updated the Help file to match the new version of the program. Also, there is no content in the Help file as of now. I would imagine Microsoft will rectify this at a later date.

js2013-09
If you check the version of Jetstress, it does show that you are running the 2013 version.

Testing Time
js2013-07
Click on ‘Start new test’.

js2013-10
Oops. Just like in previous versions of the tools you need to copy certain files from the existing Exchange installation to the directory where Jetstress is install. So find these files and copy them to your Jetstress folder:

js2013-24
Once these files are copies, close Jetstress, reopen the tool and click ‘Start new test’.

js2013-11
Jetstress will them work on the files you just copies and ask you to close again. Close the program, reopen it and click ‘Start New Test’.

js2013-12
Now Jetstress sees the files it needs and gets to the new test screen:

js2013-13
Leave the defaults and click ‘Next’.

js2013-14
Choose your test here. I selected ‘Test disk subsystem throughput’ and then clicked Next.

js2013-15
Change these numbers to how hard a resource hit you want your server to take. Usually the defaults are fine unless you are trying a particular scenario.

js2013-16
For my test I am leaving the defaults (Performance and Run background maint.) Click Next.

js2013-17
Leave the defaults if you want. Click Next.

js2013-18
Choose your test database and log directories. Enter them here. Enter the number of copies as well.

js2013-19
If you do not have any precreated databases to test, leave the default of ‘Create new databases’. Click Next.

js2013-20
Verify the test settings and then click ‘Run test.’

js2013-21
Argh. Looks like I need more space on my install to do my testing. I added a bunch more space and re-ran my test:

js2013-22
js2013-23
Yet another bump here. Need to make some adjustments and rerun the tests.

js2013-25
I checked the box and left it as 2 threads and then re-ran my test:

js2013-26

At last my test is finished! Now where are the results at?
Browse to the “C:\Program Files\Exchange Jetstress” directory and look for some HTML files with ‘Performance’ at the beginning of the file name. Then double click the file to get your results:

js2013-27

In my case my server failed to test well, which I would have expected since it’s an over taxed test server. In production you should hopefully not experience this issue.

More Information
As of now there is no Field Guide, however you can refer the old one until this gets updated – Download it here.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s