[mapserver-dev] EPSG File Overhead

[Steve Lime]

Out of curiosity is that with a shorted epsg file? Steve

>>> On 2/4/2009 at 2:56 PM, in message
<30fe546d0902041256h49c13b7ejefdf019f0b4e0708 at mail.gmail.com>, Paul Ramsey
<pramsey at cleverelephant.ca> wrote:
> I'm firing up Andrea's suite and getting some profiling results...
> 
> Using the tiger_pg test harness, and his default map file, with the
> EPSG codes at the top of the EPSG file, I get throughput of 35.5 req/s
> and profiling shows fscanf taking 26% of time. Editing the map file to
> replace init=epsg: entries with full proj4 definitions, and running
> again, I get throughput of 44.7 req/s and profiling shows that proj4
> overhead has dropped to invisible (probably because there are no
> actual reprojections in this test). At that point, the biggest CPU
> overhead is compressing the output GIF, so we're going very well
> indeed.
> _______________________________________________
> mapserver-dev mailing list
> mapserver-dev at lists.osgeo.org 
> http://lists.osgeo.org/mailman/listinfo/mapserver-dev