This year performance (load, stress) testing will be a focus track at the CMG 2007 conference. It is the best conference, by my opinion, about performance-related topics. Below is the official text:

The Computer Measurement Group (CMG) calls for papers and presentations for the 33rd International Conference to be held in San Diego, California, December 2nd through 7th, 2007. The 2007 CMG conference will cover load and stress testing, benchmarking, performance optimization, software performance engineering, resource management, capacity analysis, simulation and analytic modeling, and cost management with special emphasis on Virtualization, System Oriented Architecture (SOA), IT Service Management and IT Infrastructure Library (ITIL), and the technology implications of globalization.

I continue blog my mini-experiences . While I see almost none interested in answering my questions before myself I will provide solution I’ve applied to the problem in the initial post already. This time I want to show something about design review. If you read the design and simply try to understand what is wrong there you will most probably fail to find problems. This will be the review the developers could do. As a tester you should try to imagine how would you test it. Design tests.

Kirk proposed the "Shot in the Dark" anti-pattern. By my opinion, a must reading for all working with performance issues.

Steve Maine writes: "To recap, there are few simple rules that I'm trying to stick to as I grow this pattern. They are:
- Entities do not perform their own lifecycle management. The persistence of an entity is handled by its Repository, and its instantiation is handled via its Factory.
- Each entity talks only to its own repository.
- Repositories talk to other Repositories through the RepositoryFactory.

HiveMind is a services and configuration microkernel; an infrastructure for all types of Java applications. HiveMind encourages the use of best practices, as well as the aggressive refactoring seen in Test Driven Development.

HiveMind is responsible for thread-safe just-in-time instantiation of your services, and uses the dependency injection pattern to connect services together.

A pattern enforcing compiler™ (PEC™) allows classes to be marked as having a given design pattern, e.g. Singleton. The PEC™ then checks that the marked class conforms to the pattern and issues an error message if it does not, thus the pattern checking is much like type checking. The PECs™ downloadable from this site require no new syntax and therefore they can be used with existing: editors, IDEs, pretty printers, etc.