Orchard



== creating profiling image ==



From the base of the checkout, execute

>./build.cmd profiling



* the ./orchard.proj creates an orchard web site at ./build/Profiling

* the ./src/Orchard.Profile/profiling-setup-commands.txt holds the additional orchard.exe steps used to initialize

* the ./src/Orchard.Experimental/Commands/ProfilingCommands.cs holds an additional handful of steps to populate items



The localhost:80 web server should be pointed to the ./build/Profiling folder at this point

The "admin" password is "profiling-secret" without quotes







== repeatable load for code profiling ==



Attach your profiler to the web server

Run one of the unit tests from the ./src/Orchard.Profile class library

Each test produces a specific, repeatable set of requests against localhost:80







== stess load wcat capacity profiling ==



This will be done from a command prompt running as administrator in the ./src/Orchard.Profile folder



If wcat is not already configured for your system, execute

./src/Orchard.Profile>Initialize.cmd



To run one of the scenario scripts, like dashboard.txt, execute

./src/Orchard.Profile>Go.cmd dashboard



Scenarios are located at ./src/Orchard.Profile/Scripts with a .txt extension

They generate a variable, high level of load against localhost:80



(see wcat documentation for further information about scenario files and wcat capabilities)