Now that we've covered the configuration of your services, we'll discuss how you can monitor your BizTalk Server solution while subjecting it to load. (The techniques for applying load were covered in Chapter 8.)
Performance and scalability testing is pretty straightforward, but without following some basic principles, you can easily find yourself with an unstable system or (and often worse) no understanding of what you've changed and whether you've resolved your issue. There is one golden rule: Change one thing at a time and document everything extensively. Here is a bare-bones strategy to follow:
Decide ahead of time what the key measurement of success is going to be. Is the messages/sec (throughput) the most important metric? Is the latency of each message the critical factor?
Use a tool such as Excel to record information about each test that you perform (and include a brief description of the test's purpose). A far better alternative is to write BizUnit tests to automatically store test information in a SQL Server database. This can be customized as you require, see Chapter 8 for more information.
Assign a unique number to each test, and record a brief overview of each test (along with the result and any changes you make). The following table shows an example of such a record. You may, of course, wish to record extra columns.
This information is useful for tracking how tests have progressed. You can also add performance information such as messages/sec ...