Hi Tom,
Several things come to mind:
* all installed on the same machine? How many cores? 64bit?
* are you trying to route across your network or just draw the features?
* if you are routing you can try using a bounding box on your query to
limit the number of features returned.
* have you run a full vacuum analyse on your Postgres tables to update
statistics? How many features in your tables?
* try resetting your PostGIS connection in QGIS to not use the estimate
extent.
* spatial and attribute indexes on relevant fields in the table?
* in QGIS you can set, under Settings > Options > Rendering, to render
layers in parallel and also set the number of cores to use.
* can you set some scale dependent rendering on your layer so that it
only draws some features at small scales and then more detail as you
zoom in?
Hope that helps a bit
Cheers
Ross
On 03/11/15 19:24, Thomas Endres wrote:
Hi Everyone,
Running QGIS 2.12.0, Postgres 9.4.4, and PostGIS 2.1.7 on Ubuntu 14.04
with 16 gig RAM.
With North America OSM data loaded into postgres via osm2pgsql I am
having some extremely long project load times, even with only a single
simple layer enabled.
Progress bar runs for a very long time with no apparent visible changes.
Indexes and configuration on the db side looks good.
Wondering how to diagnose extremely slow rendering times from a local
postgres instance? Do I need to build from scratch to enable logs?
While trying to monitor the server I noticed the following:
- a few processes running SELECT st_estimatedextent....
- a few processes running FETCH FORWARD 2000 FROM...
Thanks in advance for any pointers.
-tom
_______________________________________________
Qgis-user mailing list
Qgis-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-user
_______________________________________________
Qgis-user mailing list
Qgis-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-user
