[mapguide-users] what's holding people back from upgrading to 2.0?
masonb at dfo-mpo.gc.ca
Wed Oct 8 11:16:54 EDT 2008
We had similar problems when zooming into large scales on our huge hydrology
layer for British Columbia. The server would take far too long to render a
map. We added the fix for tool tips and also turned off an annotation
layer. Now the maps are working as fast or faster than MGE2008. But I want
to get the hydrology annotations back online again. I am sure that our
users want to see the river names and lake names. So we are not out of the
> This issue is identified in RFC 52 as AGG-specific, and was in my
> initial testing as well:
> Are you seeing the same results when you switch to the GD renderer in
> -----Original Message-----
> From: Jonathan Manafi
> Subject: Re: [mapguide-users] what's holding people back from upgrading
> to 2.0?
> We experienced extreme CPU and/or memory consumption when we tested MGOS
> 2.x with some of our data. We created a ticket(#459
> https://trac.osgeo.org/mapguide/ticket/459) to document our problems,
> and I have been testing this issue with all of the updated releases, and
> I continue to see the same results. We can't zoom all the way into our
> maps without the server locking up and consuming all of the CPU, which
> is stopping us from moving a production environment to MGOS 2. We've
> been able to modify 1.2 to suit our needs for almost everything with
> plugins; and if we couldn't add a specific feature, we went in another
> So far, that has been a killer for our migration.
> mapguide-users mailing list
> mapguide-users at lists.osgeo.org
View this message in context: http://www.nabble.com/what%27s-holding-people-back-from-upgrading-to-2.0--tp19849764p19880963.html
Sent from the MapGuide Users mailing list archive at Nabble.com.
More information about the mapguide-users