RE: [mapguide-users] what's holding people back from upgrading to 2.0?
There's a code fix for this one https://trac.osgeo.org/mapguide/ticket/546. It took me a couple of iterations to get right. From what I recall, an early version of the fix is already present in MapGuide Open Source 2.0.2 build and the complete fix will be present in the MapGuide Enterprise 2009 Update. Thanks, Trevor -Original Message- From: BradM [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 08, 2008 9:40 AM To: mapguide-users@lists.osgeo.org Subject: Re: [mapguide-users] what's holding people back from upgrading to 2.0? Sorry I don't know the details. Apparently this problem was fixed with the new release of the open source version but the MGE2009 users needed to wait for an official patch. zspitzer wrote: > > out of interest what's the tool tip fix? > > On Thu, Oct 9, 2008 at 2:16 AM, BradM <[EMAIL PROTECTED]> wrote: >> >> 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 >> woods yet. >> >> >> >> JasonBirch wrote: >>> >>> This issue is identified in RFC 52 as AGG-specific, and was in my >>> initial testing as well: >>> >>> http://trac.osgeo.org/mapguide/wiki/MapGuideRfc52 >>> >>> Are you seeing the same results when you switch to the GD renderer in >>> 2.0.x? >>> >>> Jason >>> >>> -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 >>> direction. >>> >>> So far, that has been a killer for our migration. >>> ___ >>> mapguide-users mailing list >>> mapguide-users@lists.osgeo.org >>> http://lists.osgeo.org/mailman/listinfo/mapguide-users >>> >>> >> >> -- >> 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. >> >> ___ >> mapguide-users mailing list >> mapguide-users@lists.osgeo.org >> http://lists.osgeo.org/mailman/listinfo/mapguide-users >> > > > > -- > Zac Spitzer - > http://zacster.blogspot.com (My Blog) > +61 405 847 168 > ___ > mapguide-users mailing list > mapguide-users@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/mapguide-users > > -- View this message in context: http://www.nabble.com/what%27s-holding-people-back-from-upgrading-to-2.0--tp19849764p19881447.html Sent from the MapGuide Users mailing list archive at Nabble.com. ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
Re: [mapguide-users] what's holding people back from upgrading to 2.0?
One thing I think might be coming into play for slowing things down is labeling with font's using AGGspecifically very small text being fitted to complex polylines... more a hunch tho.. On Thu, Oct 9, 2008 at 2:40 AM, BradM <[EMAIL PROTECTED]> wrote: > > Sorry I don't know the details. Apparently this problem was fixed with the > new release of the open source version but the MGE2009 users needed to wait > for an official patch. > > > zspitzer wrote: >> >> out of interest what's the tool tip fix? >> >> On Thu, Oct 9, 2008 at 2:16 AM, BradM <[EMAIL PROTECTED]> wrote: >>> >>> 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 >>> woods yet. >>> >>> >>> >>> JasonBirch wrote: >>>> >>>> This issue is identified in RFC 52 as AGG-specific, and was in my >>>> initial testing as well: >>>> >>>> http://trac.osgeo.org/mapguide/wiki/MapGuideRfc52 >>>> >>>> Are you seeing the same results when you switch to the GD renderer in >>>> 2.0.x? >>>> >>>> Jason >>>> >>>> -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 >>>> direction. >>>> >>>> So far, that has been a killer for our migration. >>>> ___ >>>> mapguide-users mailing list >>>> mapguide-users@lists.osgeo.org >>>> http://lists.osgeo.org/mailman/listinfo/mapguide-users >>>> >>>> >>> >>> -- >>> 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. >>> >>> ___ >>> mapguide-users mailing list >>> mapguide-users@lists.osgeo.org >>> http://lists.osgeo.org/mailman/listinfo/mapguide-users >>> >> >> >> >> -- >> Zac Spitzer - >> http://zacster.blogspot.com (My Blog) >> +61 405 847 168 >> ___ >> mapguide-users mailing list >> mapguide-users@lists.osgeo.org >> http://lists.osgeo.org/mailman/listinfo/mapguide-users >> >> > > -- > View this message in context: > http://www.nabble.com/what%27s-holding-people-back-from-upgrading-to-2.0--tp19849764p19881447.html > Sent from the MapGuide Users mailing list archive at Nabble.com. > > ___ > mapguide-users mailing list > mapguide-users@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/mapguide-users > -- Zac Spitzer - http://zacster.blogspot.com (My Blog) +61 405 847 168 ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
Re: [mapguide-users] what's holding people back from upgrading to 2.0?
Sorry I don't know the details. Apparently this problem was fixed with the new release of the open source version but the MGE2009 users needed to wait for an official patch. zspitzer wrote: > > out of interest what's the tool tip fix? > > On Thu, Oct 9, 2008 at 2:16 AM, BradM <[EMAIL PROTECTED]> wrote: >> >> 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 >> woods yet. >> >> >> >> JasonBirch wrote: >>> >>> This issue is identified in RFC 52 as AGG-specific, and was in my >>> initial testing as well: >>> >>> http://trac.osgeo.org/mapguide/wiki/MapGuideRfc52 >>> >>> Are you seeing the same results when you switch to the GD renderer in >>> 2.0.x? >>> >>> Jason >>> >>> -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 >>> direction. >>> >>> So far, that has been a killer for our migration. >>> ___ >>> mapguide-users mailing list >>> mapguide-users@lists.osgeo.org >>> http://lists.osgeo.org/mailman/listinfo/mapguide-users >>> >>> >> >> -- >> 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. >> >> ___ >> mapguide-users mailing list >> mapguide-users@lists.osgeo.org >> http://lists.osgeo.org/mailman/listinfo/mapguide-users >> > > > > -- > Zac Spitzer - > http://zacster.blogspot.com (My Blog) > +61 405 847 168 > ___ > mapguide-users mailing list > mapguide-users@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/mapguide-users > > -- View this message in context: http://www.nabble.com/what%27s-holding-people-back-from-upgrading-to-2.0--tp19849764p19881447.html Sent from the MapGuide Users mailing list archive at Nabble.com. ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
Re: [mapguide-users] what's holding people back from upgrading to 2.0?
out of interest what's the tool tip fix? On Thu, Oct 9, 2008 at 2:16 AM, BradM <[EMAIL PROTECTED]> wrote: > > 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 > woods yet. > > > > JasonBirch wrote: >> >> This issue is identified in RFC 52 as AGG-specific, and was in my >> initial testing as well: >> >> http://trac.osgeo.org/mapguide/wiki/MapGuideRfc52 >> >> Are you seeing the same results when you switch to the GD renderer in >> 2.0.x? >> >> Jason >> >> -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 >> direction. >> >> So far, that has been a killer for our migration. >> ___ >> mapguide-users mailing list >> mapguide-users@lists.osgeo.org >> http://lists.osgeo.org/mailman/listinfo/mapguide-users >> >> > > -- > 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. > > ___ > mapguide-users mailing list > mapguide-users@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/mapguide-users > -- Zac Spitzer - http://zacster.blogspot.com (My Blog) +61 405 847 168 ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
RE: [mapguide-users] what's holding people back from upgrading to 2.0?
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 woods yet. JasonBirch wrote: > > This issue is identified in RFC 52 as AGG-specific, and was in my > initial testing as well: > > http://trac.osgeo.org/mapguide/wiki/MapGuideRfc52 > > Are you seeing the same results when you switch to the GD renderer in > 2.0.x? > > Jason > > -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 > direction. > > So far, that has been a killer for our migration. > ___ > mapguide-users mailing list > mapguide-users@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/mapguide-users > > -- 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. ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
RE: [mapguide-users] what's holding people back from upgrading to 2.0?
If Autodesk released 2.0.2 as MGE 2009 service pack I'd be happy to try it out on a very large RDBMS dataset sitting on a very busy Windows server :-) BTW, MGE 2009 performs badly (it's simply too slow, consumes enormous amounts of RAM), so we're still sticking to MGE 2008. Regards, Maksim Sestic -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Zac Spitzer Sent: Tuesday, October 07, 2008 04:02 To: MapGuide Users Mail List Subject: [mapguide-users] what's holding people back from upgrading to 2.0? There seems to be quite a few people who are sticking with 1.2 due to various issues Can people post in this thread what issues are holding them back so we can get some visibility? -- Zac Spitzer - http://zacster.blogspot.com (My Blog) +61 405 847 168 ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users __ Information from ESET NOD32 Antivirus, version of virus signature database 3495 (20081004) __ The message was checked by ESET NOD32 Antivirus. http://www.eset.com __ Information from ESET NOD32 Antivirus, version of virus signature database 3502 (20081007) __ The message was checked by ESET NOD32 Antivirus. http://www.eset.com __ Information from ESET NOD32 Antivirus, version of virus signature database 3502 (20081007) __ The message was checked by ESET NOD32 Antivirus. http://www.eset.com ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
Re: [mapguide-users] what's holding people back from upgrading to 2.0?
I have modified the viewer to prevent zooming closer than 1:100, because the server performs terrible at that point. I have logged an issue here: http://trac.osgeo.org/mapguide/ticket/523 I have not tried different styles, but I was guessing that the renderer tries to map the the entire polygon to pixels, and a building at 1:3 takes MANY pixels. Regards, Kenneth Skovhede, GEOGRAF A/S Jonathan Manafi skrev: We had some scale ranges in use that implemented some area styling, but I went ahead and added another, specifically for high zoom ranges(tried 0-1000). For our previous styling, we had a dashed line border(line04) and a feature label of the NAME property. I went ahead and just implemented a solid line border. - In the AGG renderer, hitting under 1:100 caused the server to consume steady 50% CPU. - In GD, nothing happened. The server continued to respond the same as in normal conditions. So, I tried changing the area style to a dashed line. In GD, using a dashed line caused the server to start eating up memory under 1:100, which really started occurring around 1:50. While zooming in, the memory would temporarily jump to over 200MB, and once the server was no longer using the CPU, the memory would restore itself to around 48MB. At the next zoom level, the memory would jump a little higher, perhaps 280-300MB and then restore itself. At around 1:6, the memory stayed at 520MB usage and would increase at sequential zooms. After that, the memory was never released by the server. Also, once the memory started increasing that much, the layer would no longer be displayed beyond a certain zoom scale; it seems to occur under 1:30. If I remember correctly, when I gave the layer to be tested way back when, I think Jason made a comment that this layer was made up of thousands of vertices. I understand that styling and rendering all of that data for a layer is expensive, but how come in this situation two standard styles offered by Autodesk(solid and dashed lines) differ so differently in performance? Thanks for your help. Traian Stanev wrote: Did you try to use scale ranges to control the style and visibility of the bad layer at high zoom factors? This may alleviate your problem. Traian -Original Message- From: [EMAIL PROTECTED] [mailto:mapguide-users- [EMAIL PROTECTED] On Behalf Of Jonathan Manafi Sent: Tuesday, October 07, 2008 3:57 PM To: MapGuide Users Mail List Subject: Re: [mapguide-users] what's holding people back from upgrading to 2.0? Short answer: yes. However, testing the package that is available in that ticket, I am only getting CPU load issues using the AGG renderer. The GD renderer seems to work fine with that small subset of our data. But, when I test our entire site maps with either renderer, I am still having the same issues. AGG causes CPU lockup as well as memory-hogging, and GD still causes memory-hogging. It is still being caused by the same layer, so I will see if it's possible to get an updated dataset to test with. Jason Birch wrote: This issue is identified in RFC 52 as AGG-specific, and was in my initial testing as well: http://trac.osgeo.org/mapguide/wiki/MapGuideRfc52 Are you seeing the same results when you switch to the GD renderer in 2.0.x? Jason -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 direction. So far, that has been a killer for our migration. ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
Re: [mapguide-users] what's holding people back from upgrading to 2.0?
We had some scale ranges in use that implemented some area styling, but I went ahead and added another, specifically for high zoom ranges(tried 0-1000). For our previous styling, we had a dashed line border(line04) and a feature label of the NAME property. I went ahead and just implemented a solid line border. - In the AGG renderer, hitting under 1:100 caused the server to consume steady 50% CPU. - In GD, nothing happened. The server continued to respond the same as in normal conditions. So, I tried changing the area style to a dashed line. In GD, using a dashed line caused the server to start eating up memory under 1:100, which really started occurring around 1:50. While zooming in, the memory would temporarily jump to over 200MB, and once the server was no longer using the CPU, the memory would restore itself to around 48MB. At the next zoom level, the memory would jump a little higher, perhaps 280-300MB and then restore itself. At around 1:6, the memory stayed at 520MB usage and would increase at sequential zooms. After that, the memory was never released by the server. Also, once the memory started increasing that much, the layer would no longer be displayed beyond a certain zoom scale; it seems to occur under 1:30. If I remember correctly, when I gave the layer to be tested way back when, I think Jason made a comment that this layer was made up of thousands of vertices. I understand that styling and rendering all of that data for a layer is expensive, but how come in this situation two standard styles offered by Autodesk(solid and dashed lines) differ so differently in performance? Thanks for your help. Traian Stanev wrote: Did you try to use scale ranges to control the style and visibility of the bad layer at high zoom factors? This may alleviate your problem. Traian -Original Message- From: [EMAIL PROTECTED] [mailto:mapguide-users- [EMAIL PROTECTED] On Behalf Of Jonathan Manafi Sent: Tuesday, October 07, 2008 3:57 PM To: MapGuide Users Mail List Subject: Re: [mapguide-users] what's holding people back from upgrading to 2.0? Short answer: yes. However, testing the package that is available in that ticket, I am only getting CPU load issues using the AGG renderer. The GD renderer seems to work fine with that small subset of our data. But, when I test our entire site maps with either renderer, I am still having the same issues. AGG causes CPU lockup as well as memory-hogging, and GD still causes memory-hogging. It is still being caused by the same layer, so I will see if it's possible to get an updated dataset to test with. Jason Birch wrote: This issue is identified in RFC 52 as AGG-specific, and was in my initial testing as well: http://trac.osgeo.org/mapguide/wiki/MapGuideRfc52 Are you seeing the same results when you switch to the GD renderer in 2.0.x? Jason -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 direction. So far, that has been a killer for our migration. ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
RE: [mapguide-users] what's holding people back from upgrading to 2.0?
Did you try to use scale ranges to control the style and visibility of the bad layer at high zoom factors? This may alleviate your problem. Traian > -Original Message- > From: [EMAIL PROTECTED] [mailto:mapguide-users- > [EMAIL PROTECTED] On Behalf Of Jonathan Manafi > Sent: Tuesday, October 07, 2008 3:57 PM > To: MapGuide Users Mail List > Subject: Re: [mapguide-users] what's holding people back from upgrading > to 2.0? > > Short answer: yes. > > However, testing the package that is available in that ticket, I am > only > getting CPU load issues using the AGG renderer. The GD renderer seems > to > work fine with that small subset of our data. But, when I test our > entire site maps with either renderer, I am still having the same > issues. AGG causes CPU lockup as well as memory-hogging, and GD still > causes memory-hogging. > > It is still being caused by the same layer, so I will see if it's > possible to get an updated dataset to test with. > > > Jason Birch wrote: > > This issue is identified in RFC 52 as AGG-specific, and was in my > > initial testing as well: > > > > http://trac.osgeo.org/mapguide/wiki/MapGuideRfc52 > > > > Are you seeing the same results when you switch to the GD renderer in > > 2.0.x? > > > > Jason > > > > -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 > > direction. > > > > So far, that has been a killer for our migration. > > > ___ > mapguide-users mailing list > mapguide-users@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/mapguide-users ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
RE: [mapguide-users] what's holding people back from upgrading to 2.0?
I'm using 1.2 on my release machine. It's primarily because of a bug in 2.0 which doesn't allow me to access a SDF resource after GetSelectionXML() or SetSelectionXML() is called. This is detailed in the trac ticket http://trac.osgeo.org/mapguide/ticket/524. Basically, if a user searches for a job, or parcel, then they won't be able to interact with it further because the resource will be busy. It basically negates the search function of my program, which makes the program itself pretty useless. -Mark Pendergraft -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Zac Spitzer Sent: Monday, October 06, 2008 7:02 PM To: MapGuide Users Mail List Subject: [mapguide-users] what's holding people back from upgrading to 2.0? There seems to be quite a few people who are sticking with 1.2 due to various issues Can people post in this thread what issues are holding them back so we can get some visibility? -- Zac Spitzer - http://zacster.blogspot.com (My Blog) +61 405 847 168 ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
Re: [mapguide-users] what's holding people back from upgrading to 2.0?
Short answer: yes. However, testing the package that is available in that ticket, I am only getting CPU load issues using the AGG renderer. The GD renderer seems to work fine with that small subset of our data. But, when I test our entire site maps with either renderer, I am still having the same issues. AGG causes CPU lockup as well as memory-hogging, and GD still causes memory-hogging. It is still being caused by the same layer, so I will see if it's possible to get an updated dataset to test with. Jason Birch wrote: This issue is identified in RFC 52 as AGG-specific, and was in my initial testing as well: http://trac.osgeo.org/mapguide/wiki/MapGuideRfc52 Are you seeing the same results when you switch to the GD renderer in 2.0.x? Jason -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 direction. So far, that has been a killer for our migration. ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
RE: [mapguide-users] what's holding people back from upgrading to 2.0?
This issue is identified in RFC 52 as AGG-specific, and was in my initial testing as well: http://trac.osgeo.org/mapguide/wiki/MapGuideRfc52 Are you seeing the same results when you switch to the GD renderer in 2.0.x? Jason -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 direction. So far, that has been a killer for our migration. ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
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 direction. So far, that has been a killer for our migration. Zac Spitzer wrote: even better is feedback to address this issue.. what have you gathered from the posts which make you hold back? This is really important information to share, discuss and address... z ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
Re: [mapguide-users] what's holding people back from upgrading to 2.0?
One big issue for me is the impossibility to use PostgreSQL+Postgis as database solution for geographic data. The new Postgis provider does not work (it seems to be only for windows, and not so stable). The old OGR Provider, that works fine in 1.2 ... does not work in 2.0.1 and in 2.0.2. Our build from source code doesn't work, windows binaries don't work, livecd doesn't work either. Clearly neither MGE2008. A long standing bug is opened (#666) http://trac.osgeo.org/mapguide/ticket/666 but it is not receiving any feedback (maybe the bug number is unfortunate...) Some mails to this mailing list and some questions on #mapguide and on #fdo on IRC are still waiting for answers. It appears that not so many Mapguide users are interested in Postgresql+Postgis, even if, IMHO, is one of the best RDMS for geographic data. We've seen that Mapguide 2.x has a lot of improvement over 1.2. But, as a matter of fact, does not support Postgresql+postgis. So we're stuck with old 1.2 until this problem is solved. Regards, Gabriele On Tue, Oct 7, 2008 at 12:00, Zac Spitzer <[EMAIL PROTECTED]> wrote: > even better is feedback to address this issue.. > > what have you gathered from the posts which make you hold back? > > This is really important information to share, discuss and address... > > z > > On Tue, Oct 7, 2008 at 8:55 PM, Jonio, Dennis (Aviation) > <[EMAIL PROTECTED]> wrote: >> >> Having followed the posts and ... "Better the Devil you know than the >> one you don't". >> >> r, >> dennis >> ___ >> mapguide-users mailing list >> mapguide-users@lists.osgeo.org >> http://lists.osgeo.org/mailman/listinfo/mapguide-users >> > > > > -- > Zac Spitzer - > http://zacster.blogspot.com (My Blog) > +61 405 847 168 > ___ > mapguide-users mailing list > mapguide-users@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/mapguide-users > ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
Re: [mapguide-users] what's holding people back from upgrading to 2.0?
even better is feedback to address this issue.. what have you gathered from the posts which make you hold back? This is really important information to share, discuss and address... z On Tue, Oct 7, 2008 at 8:55 PM, Jonio, Dennis (Aviation) <[EMAIL PROTECTED]> wrote: > > Having followed the posts and ... "Better the Devil you know than the > one you don't". > > r, > dennis > ___ > mapguide-users mailing list > mapguide-users@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/mapguide-users > -- Zac Spitzer - http://zacster.blogspot.com (My Blog) +61 405 847 168 ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
RE: [mapguide-users] what's holding people back from upgrading to 2.0?
Having followed the posts and ... "Better the Devil you know than the one you don't". r, dennis ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
