<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7638.1">
<TITLE>[Benchmarking] data block caching technique</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<BR>
<P><FONT SIZE=2>Hi All,<BR>
<BR>
Looking at MapServer and Geoserver results, it seems clear to me that these numbers mainly result from server-side data block caching.<BR>
<BR>
Many discussions have already been done on this subject and I think that many agree that caching data blocks and using the exact same requests in the 3 runs cannot produce realistic results. Indeed, in a realistic use-case, the exact same request with the exact same bounding box will never occur twice.<BR>
<BR>
I see that this has also been noted by Constellation-SDI during their own testing (<A HREF="http://wiki.osgeo.org/wiki/Benchmarking_2010/Constellation-SDI">http://wiki.osgeo.org/wiki/Benchmarking_2010/Constellation-SDI</A>) "Note that this is merely an academic exercise since for any non-trivial dataset, the size of data on disk will be so much larger than the size of available memory that these numbers will never be achieved". Moreover,<BR>
<BR>
We think that this combination of unrealistic test conception and data block caching technique is unfair to other participants and will make their results looks bad, while they might perform as good or even better in a real world use-case.<BR>
<BR>
I think that every one should publish all 3 run results and guarantee that these have been measured just after server restarting. We would also like that the ones using such technique rerun their test after disabling it.<BR>
<BR>
Regards,<BR>
<BR>
Luc<BR>
<BR>
ERDAS APOLLO Product Manager<BR>
ERDAS<BR>
</FONT>
</P>
</BODY>
</HTML>