[mapguide-users] DWF Viewer progress bar?

[Joel Carranza]

Thank you for this information Walt, this is helpful. The problem that 
we are seeing is that a typical map update may take anywhere between 
approx 7-12 seconds.  Half of that time is spent w/ the hourglass 
showing, and half of that time is being taken up with the progress bar 
displaying (sometimes no progress shown, sometimes halfway through). 
I've zoomed way in before, and had the map progress bar display almost 
immediately, but I still have to wait maybe 4 or 5 seconds before the 
update is complete. The number of map features we are talking about here 
is less than 10.

So what could be soaking up so much CPU/Bandwidth? This isn't exactly a 
lightweight machine (3.4 GHZ, 1GB of RAM, the server is on another 
machine but within our local network). Could it be:

- stylization? all out objects are themed with various line style and 
weights
- tooltips? Most of our map features have multi-line tooltips.
- the legend? All our layers are being displayed in the legend. When 
does this information come down?

I'm taking stabs in the dark here. Any hints might be useful.

Is it possible to hook into the DWF Viewer API to look at processing 
times on a per layer basic?

I can't seem to find the DWF Viewer API docs? Are these available on the 
web?

Final question, i promise....

Is this even the correct place to ask this question? I find myself 
confused in regard to where I should post any given question, 
considering the overlap between almost all the groups.

--Joel

Walt Welton-Lair wrote:
> The progress bar measures the total download progress for the map
> update.  Here's what happens in detail:
>
> 1/ the DWF Viewer requests a map update from the server
>    => hourglass cursor is shown, but no progress bar yet
>
> 2/ the response from the server (an EMapTransaction DWF) begins
> streaming in
>    => the progress bar is turned on and starts updating
>
> 3/ the EMapTransaction is a compressed file containing a sequence of
> resources:
>    a descriptor, graphic resources (W2Ds), and object definition data
> (attributes)
>    => while a resource is being downloaded the progress bar updates
>    => once a resource is fully downloaded it's immediately processed
>       * the progress bar does not update during processing
>       * depending on the size of the resource it may take some time
>         to process it, e.g. a layer with dense graphical data
>    => after the resource processing completes the next resource in the
> server
>       response is read
>       * the progress bar updates some more
>
> As far as the dual progress indicators, those are used in the context of
> multi-page EPlot and EModel DWFs.  One of the bars indicates the
> progress for loading the current page, while the other indicates
> progress for loading the entire DWF.  EMaps don't have multiple pages,
> and so the two indicators always have the same position.
>
> Walt
>
> -----Original Message-----
> From: mapguide-users-bounces at lists.osgeo.org
> [mailto:mapguide-users-bounces at lists.osgeo.org] On Behalf Of Joel
> Carranza
> Sent: Tuesday, February 06, 2007 10:05 PM
> To: MapGuide Users Mail List
> Subject: [mapguide-users] DWF Viewer progress bar?
>
> Perhaps this is a silly question, but here is goes:
>
> Does anybody know exactly how the progress bar in the DWF operates? On 
> each map request, there seems to be three stages...
>
> 1) No progress bar (no significant CPU activity)
> 2) Progress bar appears with very tiny amount of progress (CPU starts 
> working)
> 3) Progress bar updating and map updating (CPU is working)
>
> There are actually two different progress bars (one on top of each 
> other) which are working in tandem with each other. Does anyone know 
> precisely how to interpret them? The Below URL explains for a 
> multi-sheet DWF.
>
> http://dwf.blogs.com/beyond_the_paper/2006/09/dwf_progress_ba.html
>
> How does one interpret them in the context of a DWF map? Specifically, 
> we are wondering about the pause at stage #2. Is that when the client 
> has started recieving data, recieved all data? Is the pause at stage #2 
> utterly insignificant? Anybody know?
>
> --joel
>
>
> _______________________________________________
> mapguide-users mailing list
> mapguide-users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-users
>
> _______________________________________________
> mapguide-users mailing list
> mapguide-users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-users
>
>
>
>
>