regarding your deegree configuration problems, I would like to send you some example configuration we use here, if you let me know some email where to send it to.
Furthermore I’d like to point you to the configuration of single image files described here: http://download.deegree.org/deegree2.2/docs/deegree_wcs_documentation_en.pdf on page 18. ECW files work pretty much the same, just drop in the right bounding boxes, deegree will check the file extension to determine the file type. Configuration is spread over three XML files, but mostly straightforward.
I’d like to point out, that deegree currently is bound to a rather old version of the ECW library, which is known to have some problems.

Thanx for your efforts

Jeff McKenna probably has a 5.6 build available now… there were changes in there and in the latest GDAL/Proj that made some differences, as I recall, particularly in the raster domain. Since you’re re-running things…

P.

In my earlier tests, the extra processes didnt gain any increased throughput except on Mapserver except for ECW (tif presumabily had hit its limits)

The flip side to the fixed amount of FastCGI workers in Mapserver config is that only so much work can be done. We chose 8 workers for our 4 core system. Your system has 8 cores, so you’ll want at least 16 workers and it would be interesting to see if going to 24 improves or degrades performance.

The steep plummet of GeoServer at 80 threads speaks to something else going on, but it’ll take someone more Java-smart than me to figure that one out. I’ll point folks in the direction of your information. Great work!

Great to see you taking the lead from the vendor standpoint and very interesting results. Lets hope this and the regular FOSS4G benchmarking become the norm as these sorts of exercises are a great resource for anyone looking to select image servers.

Simon