https://issues.qgis.org/https://issues.qgis.org/favicon.ico2018-01-05T20:07:51ZQGIS Issue TrackingQGIS Application - Bug report #17809: Rendering performance issueshttps://issues.qgis.org/issues/17809?journal_id=856462018-01-05T20:07:51ZNyall Dawson
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Feedback</i></li></ul><p>Are you running a debug enabled build?</p> QGIS Application - Bug report #17809: Rendering performance issueshttps://issues.qgis.org/issues/17809?journal_id=856522018-01-06T02:18:43ZMathieu Pellerin - nIRVnirvn.asia@gmail.com
<ul></ul><p>I haven't done such test myself, but if it's not a debug-specific issue, it might have to do with QGIS 3.0 properly advertising and upgrading features to Multi*.</p> QGIS Application - Bug report #17809: Rendering performance issueshttps://issues.qgis.org/issues/17809?journal_id=856532018-01-06T06:42:02ZNyall Dawson
<ul></ul><p>I strongly suspect it's comparison between a debug enabled build (such as the osgeo4w ones) and a release build.</p> QGIS Application - Bug report #17809: Rendering performance issueshttps://issues.qgis.org/issues/17809?journal_id=856572018-01-06T09:18:44ZSaber Razmjooeisaber.razmjooei@lutraconsulting.co.uk
<ul></ul><p>I have both QGIS master and 2.18 compiled from source with pretty much the same settings (apart from qt and python).<br />Neither of them are built with debug mode enabled (CMAKE_BUILD_TYPE is left blank).</p> QGIS Application - Bug report #17809: Rendering performance issueshttps://issues.qgis.org/issues/17809?journal_id=856582018-01-06T09:18:57ZSaber Razmjooeisaber.razmjooei@lutraconsulting.co.uk
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Open</i></li></ul> QGIS Application - Bug report #17809: Rendering performance issueshttps://issues.qgis.org/issues/17809?journal_id=858112018-01-15T13:55:12ZAndreas Neumann
<ul></ul><p>Is this performance regression limited to Shapefiles or does it also surface with other data providers? Namely Geopackage or Postgis?</p> QGIS Application - Bug report #17809: Rendering performance issueshttps://issues.qgis.org/issues/17809?journal_id=858122018-01-15T14:37:01ZSaber Razmjooeisaber.razmjooei@lutraconsulting.co.uk
<ul></ul><p>Here is a zip file containing:<br /><a class="external" href="https://www.dropbox.com/s/496efk99vfspme1/17809.zip?dl=0">https://www.dropbox.com/s/496efk99vfspme1/17809.zip?dl=0</a></p>
<p>- 2 projects: one in QGIS 3 and another in QGIS 2<br />- Bot projects read the following files:<br /> - 4 layers from a geopackage file<br /> - A Shapefile<br /> - A geotiff file</p>
<p>For me, QGIS 3 project takes just over 15 seconds. QGIS 2 project takes 10 seconds. See above for my QGIS configurations and set up: both latest 2.18 and master compiled from source with no debugging and same configurations (apart from python and qt)</p> QGIS Application - Bug report #17809: Rendering performance issueshttps://issues.qgis.org/issues/17809?journal_id=858692018-01-17T03:14:56ZNyall Dawson
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Feedback</i></li></ul><p>Just to check - do you have a hidpi display?</p> QGIS Application - Bug report #17809: Rendering performance issueshttps://issues.qgis.org/issues/17809?journal_id=859582018-01-20T13:58:09ZSaber Razmjooeisaber.razmjooei@lutraconsulting.co.uk
<ul><li><strong>Operating System</strong> set to <i>Kubuntu 17.10</i></li><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Open</i></li></ul><p>Correct...it is hidpi indeed.</p> QGIS Application - Bug report #17809: Rendering performance issueshttps://issues.qgis.org/issues/17809?journal_id=859622018-01-20T19:43:15ZNyall Dawson
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Feedback</i></li></ul><p>This probably relates. Since qt5 respects hi dpi. Qgis is now drawing a LOT more pixels in the canvas (maybe 4 times as many, or even more). A good test would be to manually set your resolution to something lowdpi and compare 2.18 and 3.</p> QGIS Application - Bug report #17809: Rendering performance issueshttps://issues.qgis.org/issues/17809?journal_id=861712018-01-25T08:55:44ZSaber Razmjooeisaber.razmjooei@lutraconsulting.co.uk
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Open</i></li></ul><p>I have tested it with lower no hidpi resolution (on an external monitor) with the same results....i.e. still slower to render/load in QGIS 3 than in QGIS 2.</p> QGIS Application - Bug report #17809: Rendering performance issueshttps://issues.qgis.org/issues/17809?journal_id=866492018-02-09T07:20:38ZNyall Dawson
<ul></ul><p>Can you test <a class="external" href="https://github.com/qgis/QGIS/pull/6300">https://github.com/qgis/QGIS/pull/6300</a> ? I'm not hopeful, but that's all I was able to find by profiling. Everything else looks correct - so it's possible this is related to a Qt5 speed regression.</p> QGIS Application - Bug report #17809: Rendering performance issueshttps://issues.qgis.org/issues/17809?journal_id=866832018-02-12T00:15:58ZNyall Dawson
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Feedback</i></li></ul><p>Saber - can you please run a test of this code to determine whether the speed regression you see is related to the rendering or layer feature iteration?</p>
<pre><code>layer = iface.activeLayer()<br /> for f in layer.getFeatures():<br /> pass</code></pre>
<p>Run it over some large layers in both 2.18 and 3.0, and see if there's any significant difference in the time it takes...</p> QGIS Application - Bug report #17809: Rendering performance issueshttps://issues.qgis.org/issues/17809?journal_id=879802018-02-28T20:09:17Zmr twistervspambox-qgis@yahoo.de
<ul></ul><p>I have the same issue with large project files (many layers, many features per layer). I tested 3.0.0 and master on Windows. Not only map rendering is slow, but the whole GUI is slow - or better - laggy. Nyall, with your test I didn't get any differences.</p> QGIS Application - Bug report #17809: Rendering performance issueshttps://issues.qgis.org/issues/17809?journal_id=881842018-03-02T10:53:52Zmr twistervspambox-qgis@yahoo.de
<ul><li><strong>File</strong> <a href="/attachments/download/12318/rendering_debugging.txt">rendering_debugging.txt</a><a href="/attachments/12318/rendering_debugging.txt"><img alt="Magnifier" src="/images/magnifier.png" /></a> added</li></ul><p>I did some tests (turning labels off; removing WMS layers; disable line anti aliasing) but ditn't get any improvements.</p>
<p>I also turned on debugging for Map canvas refresh and got some warnings (see attached file).</p>
<p>Also QGIS sometimes keeps beeing listed as process in task manager after closing.</p> QGIS Application - Bug report #17809: Rendering performance issueshttps://issues.qgis.org/issues/17809?journal_id=882022018-03-02T16:07:57ZSaber Razmjooeisaber.razmjooei@lutraconsulting.co.uk
<ul></ul><p>Could you also check you are using the same settings for multi-threaded rendering?</p> QGIS Application - Bug report #17809: Rendering performance issueshttps://issues.qgis.org/issues/17809?journal_id=882502018-03-03T17:31:16ZGiovanni Manghigiovanni.manghi@gmail.com
<ul><li><strong>Regression?</strong> changed from <i>No</i> to <i>Yes</i></li></ul> QGIS Application - Bug report #17809: Rendering performance issueshttps://issues.qgis.org/issues/17809?journal_id=883082018-03-05T11:24:59Zmr twistervspambox-qgis@yahoo.de
<ul></ul><p>Saber Razmjooei wrote:</p>
<blockquote>
<p>Could you also check you are using the same settings for multi-threaded rendering?</p>
</blockquote>
<p>It makes no difference whether multi-threaded rendering is activated or not.</p> QGIS Application - Bug report #17809: Rendering performance issueshttps://issues.qgis.org/issues/17809?journal_id=883492018-03-06T10:43:46ZGiovanni Manghigiovanni.manghi@gmail.com
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Open</i></li></ul> QGIS Application - Bug report #17809: Rendering performance issueshttps://issues.qgis.org/issues/17809?journal_id=887382018-03-14T17:32:30ZJustin Gamblejgamble@ci.oceanside.ca.us
<ul></ul><p>Same here, running QGIS 3.0 on Windows 7. Have built 2 large projects (10+ layers) and even with only simple polyline features rendering is very slow</p> QGIS Application - Bug report #17809: Rendering performance issueshttps://issues.qgis.org/issues/17809?journal_id=887412018-03-14T20:48:35ZNyall Dawson
<ul></ul><p>There's really nothing we can do without more troubleshooting here -- there must be something specific to the setups or data where this issue is encountered, and that's what we need to know.</p> QGIS Application - Bug report #17809: Rendering performance issueshttps://issues.qgis.org/issues/17809?journal_id=887422018-03-15T00:53:39ZNyall Dawson
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Feedback</i></li></ul> QGIS Application - Bug report #17809: Rendering performance issueshttps://issues.qgis.org/issues/17809?journal_id=887612018-03-15T11:07:50ZGiovanni Manghigiovanni.manghi@gmail.com
<ul></ul><p>maybe is related to the slowness many are seeing in rendering of postgis layers?</p> QGIS Application - Bug report #17809: Rendering performance issueshttps://issues.qgis.org/issues/17809?journal_id=887622018-03-15T11:14:49ZSaber Razmjooeisaber.razmjooei@lutraconsulting.co.uk
<ul><li><strong>Operating System</strong> deleted (<del><i>Kubuntu 17.10</i></del>)</li></ul><p>Please see the link to the example file I have posted earlier, which is based on flat files (gpkg):<br /><a class="external" href="https://www.dropbox.com/s/496efk99vfspme1/17809.zip?dl=0">https://www.dropbox.com/s/496efk99vfspme1/17809.zip?dl=0</a></p>
<p>It will be great if someone else could test this project and report the rendering time in QGIS 2.18 and 3.0</p> QGIS Application - Bug report #17809: Rendering performance issueshttps://issues.qgis.org/issues/17809?journal_id=887802018-03-15T21:21:42ZNyall Dawson
<ul></ul><p>Saber - I tested that project, no issue here.</p> QGIS Application - Bug report #17809: Rendering performance issueshttps://issues.qgis.org/issues/17809?journal_id=892272018-04-12T08:55:15Zmr twistervspambox-qgis@yahoo.de
<ul></ul><p>I did some research with Saber's and my projects: Both run smoothly when stored on a local path. However when loaded from a network drive, QGIS 3 is getting slow. With QGIS 2.18 I have no such problems - it makes no difference whether the files are stored on a network drive or locally.</p> QGIS Application - Bug report #17809: Rendering performance issueshttps://issues.qgis.org/issues/17809?journal_id=906052018-06-29T13:39:03Zmr twistervspambox-qgis@yahoo.de
<ul></ul><p>Still present in 3.2. Could this be related with the following QT-issue? <a class="external" href="https://bugreports.qt.io/browse/QTBUG-13182?focusedCommentId=201836&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-201836">https://bugreports.qt.io/browse/QTBUG-13182?focusedCommentId=201836&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-201836</a></p> QGIS Application - Bug report #17809: Rendering performance issueshttps://issues.qgis.org/issues/17809?journal_id=908932018-07-17T20:48:42ZSpencer Gardnerspencergardner@gmail.com
<ul></ul><p>I've experienced <em>very</em> slow rendering times as well that I think must be related. In my case it's with PostGIS layers pulled over our network. The slowdown seems to be related to network latency. When I use layers on a PostGIS server in my local network things aren't terribly slow. When I reference a layer on a server across the country it's painfully slow. This was never an issue in the 2.x series.</p>
<p>I'd love to help troubleshoot further but I'm not sure what info can be useful at this point.</p> QGIS Application - Bug report #17809: Rendering performance issueshttps://issues.qgis.org/issues/17809?journal_id=908942018-07-17T23:47:19ZNyall Dawson
<ul></ul><p>Spencer are you on 3.2?</p> QGIS Application - Bug report #17809: Rendering performance issueshttps://issues.qgis.org/issues/17809?journal_id=912542018-08-04T00:19:46ZWillem Buitendyk
<ul></ul><p>QGIS 3.2.1 on the Mac has far too many network issues. WFS 1.0, 1.1 or 2.0 won't work at all - network timeouts. Postgis will load the data but the attribute data will show 'error' in every field. On windows WFS 1.0 and 1.1 will work but the data comes in one big lump instead of incrementally like QGIS 2.18 or possibly even QGIS 3.1? I was about to try under linux but might leave that for another day.</p> QGIS Application - Bug report #17809: Rendering performance issueshttps://issues.qgis.org/issues/17809?journal_id=912612018-08-04T08:34:01ZGiovanni Manghigiovanni.manghi@gmail.com
<ul></ul><p>Willem Buitendyk wrote:</p>
<blockquote>
<p>QGIS 3.2.1 on the Mac has far too many network issues. WFS 1.0, 1.1 or 2.0 won't work at all - network timeouts.</p>
</blockquote>
<p>so the same exact layers/connections work without issues on 2.18? Can you share the url?</p>
<blockquote>
<p>Postgis will load the data but the attribute data will show 'error' in every field.</p>
</blockquote>
<p>the same datasource is ok on 2.18?</p> QGIS Application - Bug report #17809: Rendering performance issueshttps://issues.qgis.org/issues/17809?journal_id=960102018-11-13T07:50:21Zmr twistervspambox-qgis@yahoo.de
<ul><li><strong>File</strong> <a href="/attachments/download/13762/3.5.LOG">3.5.LOG</a><a href="/attachments/13762/3.5.LOG"><img alt="Magnifier" src="/images/magnifier.png" /></a> added</li></ul><p>Since I still have this issue, I tested the 3.5.0 nightly build. With DebugView I get two different and constantly repeating warnings (see full log attached). With 2.18.25 nightly there are no such warnings.<br /><pre>
00000215 31.26636505 [7316] ..\..\..\src\core\raster\qgsrasterlayerrenderer.cpp(140) : (QgsRasterLayerRenderer::QgsRasterLayerRenderer) [78ms] draw request outside view extent.
00000216 31.26671982 [7316] ..\..\..\src\core\raster\qgsrasterlayerrenderer.cpp(140) : (QgsRasterLayerRenderer::QgsRasterLayerRenderer) [0ms] draw request outside view extent.
00000217 31.26707649 [7316] ..\..\..\src\core\raster\qgsrasterlayerrenderer.cpp(140) : (QgsRasterLayerRenderer::QgsRasterLayerRenderer) [0ms] draw request outside view extent.
00000218 34.49539948 [7316] ..\..\..\src\providers\ogr\qgsogrprovider.cpp(3456) : (QgsOgrProvider::crs) [3229ms] no spatial reference found
00000219 34.50426865 [7316] ..\..\..\src\providers\ogr\qgsogrprovider.cpp(3456) : (QgsOgrProvider::crs) [16ms] no spatial reference found
00000220 34.52859497 [7316] ..\..\..\src\core\raster\qgsrasterlayerrenderer.cpp(140) : (QgsRasterLayerRenderer::QgsRasterLayerRenderer) [31ms] draw request outside view extent.
00000221 34.52896881 [7316] ..\..\..\src\core\raster\qgsrasterlayerrenderer.cpp(140) : (QgsRasterLayerRenderer::QgsRasterLayerRenderer) [0ms] draw request outside view extent.
00000222 34.57506180 [7316] ..\..\..\src\core\raster\qgsrasterlayerrenderer.cpp(140) : (QgsRasterLayerRenderer::QgsRasterLayerRenderer) [47ms] draw request outside view extent.
00000223 34.57543182 [7316] ..\..\..\src\core\raster\qgsrasterlayerrenderer.cpp(140) : (QgsRasterLayerRenderer::QgsRasterLayerRenderer) [0ms] draw request outside view extent.
00000224 34.57579803 [7316] ..\..\..\src\core\raster\qgsrasterlayerrenderer.cpp(140) : (QgsRasterLayerRenderer::QgsRasterLayerRenderer) [0ms] draw request outside view extent.
</pre></p> QGIS Application - Bug report #17809: Rendering performance issueshttps://issues.qgis.org/issues/17809?journal_id=982012019-01-14T22:58:47ZNyall Dawson
<ul><li><strong>Resolution</strong> set to <i>not reproducable</i></li><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Closed</i></li></ul><p>Closing this report -- it's become a mix of conflicting possibly-related issues. Let's open specific issues if there's outstanding issues still in 3.4.3</p> QGIS Application - Bug report #17809: Rendering performance issueshttps://issues.qgis.org/issues/17809?journal_id=1042112019-04-25T12:43:34Zmr twistervspambox-qgis@yahoo.de
<ul></ul><p>For me this issue is solved by replacing our old network storage (Netgear ReadyNAS Duo) with a new device. I think the cause of this issue was a high network latency of the old NAS in combination with Qt 5.x.</p>