Perfstat for Windows GUI

by NetApp Employee on ‎2013-06-18 11:55 AM - edited on ‎2014-09-25 04:08 PM by Community Manager

The NetApp Perfstat utility is a great utility; however, it takes some effort to set it up inside of a Windows environment.  Sometimes that effort occurs during a high stress time while a performance issue is actually occurring.  There is a great GUI from fellow NetApp engineer Nuno (see; however, some customers have requested a utility that is not a compiled application.  For all these reasons I put together the Perfstat for Windows GUI.


Attached you will find the GUI  (PerfstatGUI.hta).  Simply launch it on any Windows machine you wish to run Perfstat on.  There is a basic read me when you first launch the tool (also attached here is a PDF of the entire Perfstat GUI Read Me).  In addition there is attached PerfstatScriptTemplate.vbs which is a template for a script that can be ran outside the GUI (i.e. through a scheduled task).  If you wish to use the script, select the option "Create Script Only" under the perfstat options in the PerfstatGUI tool and you will be provided instructions on how to use the template.


Current Versions:


August 28, 2014 Update Version 2.5

-Made the logging window scroll to the bottom after adding log information

-Added an option to prevent AutoSupport generation when running Perfstat



March 5, 2014 Update Version 1.1

-Changed the way perfstat 7 was executed to account for the way DOS handles output files


All previous update notes are included in the files.  Just open in notepad if you wish to read through the updates.


Please post all comments and suggestions for improvements here.

on ‎2014-01-27 10:54 AM

Getting the following errror: 1-27-2014 1-56-02 PM.png

NetApp Employee on ‎2014-01-27 11:22 AM


Thanks for the feedback!  That particular line it calls out looks at the contents of a zip file (depending upon where you were in the process either the or one of the perfstat*.zip files).  A couple of quick thoughts.  Can you check if you have the patch described in this article:  Can you manually unzip the .zip file and if so does it use the built in Windows zip tools?  Any chance compressed folders are disabled like here:

on ‎2014-01-27 04:00 PM

When it looks for the perfstat zip, does it look for just the name, or or does it try to look for a file called perfstat with the ext of .zip?

NetApp Employee on ‎2014-01-28 04:59 AM

Ahh - perfect question!  So first it looks for either perfstat.exe or perfstat8.exe and if not found it looks for either perfstat7* or perfstat8* but I realize it could find another file similarly named that doesn't have a .zip extension that it might try to extract.  I'll change that in the code.  Is that perhaps what's happening here, a different file matching one of those patterns?  Thanks much for the feedback as well, it is certainly helpful to knock out these problems.

on ‎2014-01-28 05:37 AM

OK that makes sense and answered my question. With the perfstat release date being presented in the file name (i.e. ) I wasn't sure if the script is adaptable to look for the file with that information. I thought that might be the problem that was occurring, but with your last reply it seems you factored that in. Currently I have two zip files located with the .hta directory. OpenSSH and perfstat7. Not sure what else could be causing it minus maybe going in and unblocking the zip folder which I completely forgot to do as well. I'll run the test today now that I've unlocked the files and see if that doesn't resolve the issue.

NetApp Employee on ‎2014-03-12 01:29 AM

Hi Tim

I just spotted that the openssh link ( ) in your readme PDF is non existent anymore.

NetApp Employee on ‎2014-03-12 05:39 AM

Nice find Patrick!  Short story, I've got it fixed now.  Longer story, I'm working through the read me and about 3/4 of the way through I realize I've been a little lazy and sometimes capitalized the P in Perfstat and sometimes I didn't.  So I did a global search and replace.  Well, that also replaced it in the links which clobbered our case-sensitive URLs on the support site.  I went through and updated them all now correctly.  The only trouble you might have is the link for plink.  The link is correct but there are some versions of Adobe Reader that don't know what to do with a URL with a tilde character in it and seemingly just freeze up on that link.

NetApp Employee on ‎2014-04-28 12:14 PM

Just a general note on compatibility.  If you are seeing either of these errors:

"ssh-keygen.exe is not a valid Win32 application"

"0 [main] 3360 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer"

It is likely due to a compatibility of the version of OpenSSH from our support site and your particular version of Windows.  There are other versions of OpenSSH built for Windows 64-bit available.  Obviously I am unable to recommend or provide warranty for any products outside of NetApp control - there is one such build available here:

on ‎2014-07-02 03:30 PM

Hi just installed this software on one of our production servers. The utility has a major flaw in it.

When you run to copy ssh keys to the filer. It does 2 things wrong?

1. It moves the authorized_keys to a backup. It should be doing a copy of the file before it write the keys into it. This is oversite and certain not good programming style.

2. It need to check to see if the user exists on the filer. It makes no assumption that I may have already setup keys already on it.

Even if I correct the item #1. It still does not work and does not allow me to get perfstat at all.

I don't know why this should work even on CLI on a stupid windows platform.

on ‎2014-07-23 08:57 PM

Can you please share us a video of the whole process which will help for the beginners aswell to do better with your tool.


NetApp Employee on ‎2014-07-25 07:52 AM

Great suggestion!  I'll get working on that.  I'm finishing up another project so might take some time, but will definitely do it.


This NetApp Community is public and open website that is indexed by search engines such as Google. Participation in the NetApp Community is voluntary. All content posted on the NetApp Community is publicly viewable and available. This includes the rich text editor which is not encrypted for https.

In accordance to our Code of Conduct and Community Terms of Use DO NOT post or attach the following:

  • Software files (compressed or uncompressed)
  • Files that require an End User License Agreement (EULA)
  • Confidential information
  • Personal data you do not want publicly available
  • Another’s personally identifiable information
  • Copyrighted materials without the permission of the copyright owner

Files and content that do not abide by the Community Terms of Use or Code of Conduct will be removed. Continued non-compliance may result in NetApp Community account restrictions or termination.