This graph shows two important scalability measures, number of request per second (mean) returned by DBPrism CMS and time per request across all concurrent request (mean).

The hardware used for this test was a server machine with PIII processor and 512 Mb of ram running Linux Mandrake 8.2, Oracle 9.2.0 and OC4J 9.0.2.
Red bar shows number of request per second served by DBPrism CMS according with 1, 2, 5 up to 40 concurrent request. Note that, increasing the number of concurrent user does not impact into the performance result, it mean that from 25 concurrent request in advance the number of returned request per second is stabilized around 20.
Brown bar shows time per request, mean across all concurrent request in milliseconds. Like the other measure this graph shows that, incrementing the concurrent user do not impact in the average response time result by DBPrism CMS. This time tend to stabilize in 45 milliseconds at 25 concurrent request.
Finally this shows that for the given hardware the site can perfectly manage a web site with 2 million pages view a day with peak of 40 concurrent request (800 user on line).

next in this section ESI invalidation protocol