Network Computingwww.networkcomputing.com

Exodus Performance Labs' StressPoint makes some of the same recommendations the other monitors make, but understanding how it got to those results is difficult. Not impossible -- just difficult.

Exodus performed more separate tests (six, to be exact) than any other vendor in our roundup. As with the other vendors, Exodus loaded the site with a random mix of browsing and searches touching on the most used portions. All the subsequent tests focused on separate sections of the site. The reports annotated most of the test but left out portions. We ended our testing with low confidence in the results.

StressPoint's top-level results were similar to Active Test's. Exodus showed a slightly more conservative 240-user load to Mercury's 260, before response time exceeded the magic eight-second mark.

Each of the graphs showed the load and test values over that load. Most of the graphs supported the summarized results of 240 users as the point at which eight seconds began to be violated and 320 users as the point where all pages were loading at rates longer than eight seconds (see screen, below).

We expected the first test, which did some general browsing and data lookup, to be the benchmarking load. That is to say, we thought it would represent a normal mix of users doing what normal users do concurrently on the site. However, the first test was plagued with errors at load levels as low as 120 users and never went beyond 180 users. The overall results of the first test were sketchy and without a performance graph, forcing us to piece together what happened using a server log chronicle.

Exodus Performance Labs' StressPoint Click here to enlarge