<div dir="ltr">Hi Ross - thanks for your suggestions. See notes below.<div><br></div><div><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div text="#000000" bgcolor="#FFFFFF">* all installed on the same machine? How many cores? 64bit?<br></div></blockquote><div>Yes - all on same machine - 4 cores - 64 bit</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div text="#000000" bgcolor="#FFFFFF">
* are you trying to route across your network or just draw the
features? </div></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div text="#000000" bgcolor="#FFFFFF">
* if you are routing you can try using a bounding box on your query
to limit the number of features returned.<br></div></blockquote><div>No routing - just drawing.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div text="#000000" bgcolor="#FFFFFF">
* have you run a full vacuum analyse on your Postgres tables to
update statistics? How many features in your tables?<br></div></blockquote><div>Yes and repeated just to make sure - no difference.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div text="#000000" bgcolor="#FFFFFF">
* try resetting your PostGIS connection in QGIS to not use the
estimate extent.<br></div></blockquote><div>Where is this setting in QGIS?</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div text="#000000" bgcolor="#FFFFFF">
* spatial and attribute indexes on relevant fields in the table?<br></div></blockquote><div>Yes</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div text="#000000" bgcolor="#FFFFFF">
* in QGIS you can set, under Settings > Options > Rendering,
to render layers in parallel and also set the number of cores to
use.<br></div></blockquote><div>Already set to render layers in parallel and using all 4 cores.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div text="#000000" bgcolor="#FFFFFF">
* 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?<br></div></blockquote><div><br></div><div>I hope to when I can get that far. Are you using North America OSM data without issues?</div><div>Wishing I could see why QGIS is taking up so much CPU for so long w/PostGIS when trying to load a project.</div><div>Strange behavior - looking for any tools to troubleshoot and provide more information.</div><div><br></div><div>Thanks again,</div><div>-tom</div><div><br></div><div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div text="#000000" bgcolor="#FFFFFF"><div><div><br>
<br>
<div>On 03/11/15 19:24, Thomas Endres wrote:<br>
</div>
</div></div><blockquote type="cite"><div><div>
<div dir="ltr">
<div>Hi Everyone,</div>
<div>Running QGIS 2.12.0, Postgres 9.4.4, and PostGIS 2.1.7 on
Ubuntu 14.04 with 16 gig RAM.</div>
<div><br>
</div>
<div>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.</div>
<div>Progress bar runs for a very long time with no apparent
visible changes.</div>
<div>Indexes and configuration on the db side looks good.</div>
<div>Wondering how to diagnose extremely slow rendering times
from a local postgres instance? Do I need to build from
scratch to enable logs?</div>
<div>While trying to monitor the server I noticed the following:</div>
<div>- a few processes running SELECT st_estimatedextent....</div>
<div>- a few processes running FETCH FORWARD 2000 FROM...</div>
<div><br>
</div>
<div>Thanks in advance for any pointers.</div>
<div>-tom</div>
</div>
<br>
<fieldset></fieldset>
<br>
</div></div><pre>_______________________________________________
Qgis-user mailing list
<a href="mailto:Qgis-user@lists.osgeo.org" target="_blank">Qgis-user@lists.osgeo.org</a>
<a href="http://lists.osgeo.org/mailman/listinfo/qgis-user" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-user</a></pre>
</blockquote>
<br>
</div>
<br>_______________________________________________<br>
Qgis-user mailing list<br>
<a href="mailto:Qgis-user@lists.osgeo.org" target="_blank">Qgis-user@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/qgis-user" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-user</a><br></blockquote></div><br></div></div></div>