[Spam: 3.72] RE: [mapguide-users] PostGIS - whatiswrongwhitthat?- my todo list

[Paul Ramsey]

Also, turn on statement logging in postgresql.conf 
<http://www.postgresql.org/docs/8.1/interactive/runtime-config-logging.html#GUC-LOG-STATEMENT> 
and see what SQL your driver is generating. It could be quite 
inefficient for your use case ("gimmee all them features in this box!")

P

Jason Birch wrote:
> 100K polygons is not such a great idea, but out of the box PostgreSQL is
> not well tuned for PostGIS.  Can you try some of the stepps here and see
> if you notice a difference?
> 
> http://postgis.refractions.net/pipermail/postgis-users/2006-March/011539
> .html
> 
> Jason 
> 
> -----Original Message-----
> From: mapguide-users-bounces at lists.osgeo.org
> [mailto:mapguide-users-bounces at lists.osgeo.org] On Behalf Of Traian
> Stanev
> Sent: Thursday, February 01, 2007 08:07
> To: MapGuide Users Mail List
> Subject: RE: [Spam: 3.72] RE: [mapguide-users] PostGIS -
> whatiswrongwhitthat?- my todo list
> 
> 
> I just tried it with a layer with 100K polygons. It takes about 70
> seconds for the layer to preview in MapGuide. I was watching the CPU
> usage during that time and about 70% of the time was spent in the
> postgres process (the rest was in the mgserver process, which includes
> the provider logic and OGR itself, and the rendering of the layer). So I
> place the blame on Postgres. I verified that the spatial indexing works
> -- once I zoom in things get much faster.
> 
> Traian
>  
> _______________________________________________
> mapguide-users mailing list
> mapguide-users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-users


-- 

   Paul Ramsey
   Refractions Research
   http://www.refractions.net
   pramsey at refractions.net
   Phone: 250-383-3022
   Cell: 250-885-0632