RE: Windows User Simulation Tool
Mickey Lane <[email protected]> Fri, 11 Sep 2009 12:57:09 -0400
| Newsgroups | gmane.comp.file-systems.openafs.devel.win32 |
|---|---|
| Message-ID | <002301ca3300$e7c822b0$b7586810$@com> |
Interesting stuff. WRT AFS, is there any difference between having say 3 processes each = with 3 test threads vs. 1 process with 9 test threads? Mickey. > -----Original Message----- > From: Jeffrey Altman [mailto:[email protected]] > Sent: Friday, September 11, 2009 10:20 AM > To: Mickey Lane > Cc: [email protected] > Subject: Re: [OpenAFS-win32-devel] Windows User Simulation Tool >=20 > Mickey Lane wrote: > > Are there any notes on this? What it does? How to use it? >=20 > The original author, David Tanner, presented on the tool at the 2006 > Best Practices Workshop. >=20 > As with most of OpenAFS, the command line usage text and the source > code > are the documentation. In brief: >=20 > wintorture.exe is a scripting engine that creates multiple threads > executing the scripted instructions provided by the specified > script. >=20 > stress.exe manages multiple instances of wintorture.exe and > coordinates the compilation of statistics from each of them > upon completion. >=20 > stopstress.exe permits you to pause, resume, and stop > all tests. >=20 > Sample scripts are provided in the tests/torture/clients directory. >=20 > > Also - I don't see anything that looks like GUI code in or around = the > src/WINNT/tests area. >=20 > The UI is called StressUI and apparently David didn't include its > source > in the contribution. I've posted a screenshot at >=20 > http://www.secure-endpoints.com/images/stressui.png >=20 > It really is just a guified version of stress.exe. Reproducing it > should not take more than an hour or so. I didn't notice because I > never used the tool. Command line scripting is more powerful.