Web performance in seven steps; Step 4: Test continuously
Posted by Jeroen Borgers at around evening time: July 22nd, 2009
Last time I blogged about the importance of representative performance testing. Having production-like properties for hardware, OS, JVM, app server, database, external systems and simulated user load are essential to prevent bad performance surprises when going live. In addition, I described how cloud computing can be utilized to generate high loads on-demand without having to worry about the infrastructure.
Continuous performance testing
With a representative test as one of the last steps before going live we prevent that expensive bad-performance surprises will pop up in production. However, the same surprises will pop-up, only earlier and with less impact. To save costs and prevent large architectural refactoring, it is crucial to test for performance as soon as possible. This is just like any other software defects and Quality Assurance: the later in the development process defects are detected, the more costly these defects are.
At a popular web shop I had the following challenge: (more...)
Training
Categories
- Java (291)
- Agile (127)
- General (96)
- Architecture (47)
- Testing (45)
- Scrum (44)
- Performance (42)
- Podcast (31)
- SOA (25)
- Middleware (31)
- Deployment (20)
- Project Management (23)
- Xebia Labs (21)
- Quality Assurance (16)
- Tools (12)
- lean architecture (11)
- Articles (9)
- Virtualization (9)
- Security (7)