[mapguide-users] performance problems

[Walt Welton-Lair]

One possibility is that the DWF Viewer is still busy triangulating the geometry.  What happens is that the viewer processes the geometry first (in your case the first 90%), triangulates it, and then processes the remaining pieces (the attributes).  If you have lots of complicated polygons in your map then triangulating can take some time.
 
When the viewer is at 90% is the CPU still going?  If so does the load complete if you wait?
 
Walt

  _____  

From: Marko Podgoršek [mailto:Marko.Podgorsek at kaliopa.si] 
Sent: Friday, April 14, 2006 5:57 AM
To: users at mapguide.osgeo.org
Subject: [mapguide-users] performance problems


Good day Marko.
 
Could you provide more details please?
 
For example:
 
- the type and number of processors
- the MGHz of the system
- the amount of RAM the system has
- are there any other applications or web applications on the server
- are you running Studio on the same machine or a separate client
 
If the dwf viewer is stopping it's possible the system is timing out which is a symptom of the performance issue.
 
One possibility is that if you don't have enough physical memory the system is swapping to virtual memory.
 
Regards,
Dave Wilson
 
Hi:
I'm using 2.4GHz P4 with 1GB of ram. It's a test computer (my work computer). 
There are no other web apps on the computer. I'm not running Studio. I just want to try out the sample map (Sheboygan.mgp)
 
I found out why is it working so slow. PANDA ANTIVIRUS. Don't use it :)
Now it's fast.
But still...Dwf viewer still stops at about 90%. Why is that?
 


--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.385 / Virus Database: 268.4.1/311 - Release Date: 13.4.2006


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/mapguide-users/attachments/20060414/3904670c/attachment.html