[Chameleon] performance of drawmap.php

[Bart van den Eijnden]

Hi Daniel,

I am using 4.2, that's right.

I tried the DEBUG in MAP and LAYER (of the Chameleon app MAP file) but am 
not getting anything into the Apache error log concerning times. It would 
be very useful to have this option built into the maptools Windows 
binaries.

If we would use your example to determine the overhead caused by the WMS 
client (downloading through Mapserver WMS client, compared to downloading 
 from the WMS server directly):

(3.045-2.392)/3.045 = 20%

I may be misinterpreting the data though .....

In my example I had 300 ms / 833 ms = 36% overhead (1 WMS layer, localhost)

But maybe the conclusion of this all is that, the fact that the map 
rendering does not start immediately, is the bottle neck in this case, and 
that's a hard one to solve.

Best regards,
Bart

On Tue, 01 Jun 2004 13:52:43 -0400, Daniel Morissette 
<dmorissette at dmsolutions.ca> wrote:

> bartvde at xs4all.nl wrote:
>>
>> Paul, there must be something pretty slow in Mapserver WMS client or 
>> not?
>> Or can you think of any other cause for this? Can Daniel provide any
>> insight into this?
>>
>
> I'm assuming that you're using MapServer 4.2, correct?
>
> You could see where the time is spent by setting DEBUG TRUE in the 
> client mapfile at the map level and inside each layer of interest.  You 
> also need a build with --enable-debug on Linux/Unix, or with 
> -DENABLE_STDERR_DEBUG -DNEED_NONBLOCKING_STDERR on Windows.  I don't 
> know if our windows builds on maptools include that option or not, Paul 
> should know.
>
> The Apache error_log will contain detailed times for each layer and for 
> the full map draw. I copied below an example where we request 7 layers 
> from the GMap WMS.  As you'll notice, a single WMS client request is 
> issued because MapServer detects that all layers come from the same 
> server and combines them.
>
> Daniel



--