In the past, we’ve blogged about our performance tests but in the chaos of our various development cycles we never really institutionalized such tests.
We are now reaching the point as we push towards our first release that we need to assure that performance considerations are met. One move in this direction was our use of Hudson as a base for building ESME on a daily basis. Now, we’ve started examining our performance in detail by planning a series of performance tests to examine ESME in various configurations (cloud-based, on-premise, etc.). The goal is to establish a performance testing component as part of our continuous integration efforts. There is now a Apache wiki page where the various performance test configurations and the performance test results will be listed.
We already started with this increased focus on performance tests with an initial test conducted by Markus Kohler on 2009-11-19. Here is a screenshot from this test.
The results of this test are described in full detail here.
For us, the most important thing is to establish a structure and format for such tests that makes it easy for us and ESME users to be able to compare results in a logical fashion. It is only so that users can decide what sort of infrastructure is necessary for their respective ESME installations.
