https://issues.qgis.org/https://issues.qgis.org/favicon.ico2014-11-12T11:30:06ZQGIS Issue TrackingQGIS Application - Bug report #11631: field calculator update is very slowhttps://issues.qgis.org/issues/11631?journal_id=574202014-11-12T11:30:06ZGiovanni Manghigiovanni.manghi@gmail.com
<ul><li><strong>Category</strong> set to <i>Field calculator</i></li><li><strong>Status</strong> changed from <i>Open</i> to <i>Feedback</i></li></ul><p>do you see any difference if you use the FC with the table of attributes open or closed?</p> QGIS Application - Bug report #11631: field calculator update is very slowhttps://issues.qgis.org/issues/11631?journal_id=574282014-11-13T00:11:55ZGavin Fleminggavin@kartoza.com
<ul></ul><p>540000 road LineString records, 8 core i7 with SSD, 8GB RAM</p>
<p>no difference updating 17 records whether table is open or not, both 30s.</p>
<p>Opening the table just adds another looong wait (how can this be minimised?).</p> QGIS Application - Bug report #11631: field calculator update is very slowhttps://issues.qgis.org/issues/11631?journal_id=574312014-11-13T01:24:24ZGiovanni Manghigiovanni.manghi@gmail.com
<ul></ul><p>Gavin Fleming wrote:</p>
<blockquote>
<p>540000 road LineString records, 8 core i7 with SSD, 8GB RAM</p>
<p>no difference updating 17 records whether table is open or not, both 30s.</p>
<p>Opening the table just adds another looong wait (how can this be minimised?).</p>
</blockquote>
<p>postgis?</p> QGIS Application - Bug report #11631: field calculator update is very slowhttps://issues.qgis.org/issues/11631?journal_id=574332014-11-13T01:33:19ZGavin Fleminggavin@kartoza.com
<ul></ul><p>local PostgreSQL 9.3, PostGIS 2.1</p> QGIS Application - Bug report #11631: field calculator update is very slowhttps://issues.qgis.org/issues/11631?journal_id=574432014-11-13T12:56:20ZGiovanni Manghigiovanni.manghi@gmail.com
<ul></ul><p>Gavin Fleming wrote:</p>
<blockquote>
<p>540000 road LineString records, 8 core i7 with SSD, 8GB RAM</p>
<p>no difference updating 17 records whether table is open or not, both 30s.</p>
<p>Opening the table just adds another looong wait (how can this be minimised?).</p>
</blockquote>
<p>I'm really not lucky as it doesn't seem I'm able to replicate any of the issues you file :)</p>
<p>In this case:</p>
<ul>
<li>I downloaded the OSM UK roads shape, 3 million features and imported it into a local postgis installation (9.3, Linux, 4 cores, 8gb ram and SSD).</li>
</ul>
<ul>
<li>selected a few tens of records/features (20/30) and updated an attribute.</li>
</ul>
<ul>
<li>repeated the above after selecting ~200k features</li>
</ul>
<p>results:</p>
<p>in both cases the update operation, after clicking the "ok" button in the field calculator, takes a few seconds (eventually what can be surprising is the fact that the time it takes does not seems to differ much between a few records selected and a lot of records selected).</p>
<p>In the past we had issues when updating (or creating) fields with the FC and at the same time having the table of attributes open. I remember also another similar issue that was related to the number of features that were visible the moment the FC was used. In both cases fixes/patches has been applied and the situation is much better now.</p>
<p>Opening a 3 million table of attributes table here take ~25 seconds from shapefile and ~40 from postgis.</p>
<p>Unchecking the "select at id" option when loading the postgis layer make a little faster the operation, ~30 seconds, but in this case there may be a bug as the <strong>operation is done 2 times</strong> (to notice is necessary to open a postgis table of at least 80/100k features). Jurgen, is this right?</p>
<p>To make faster opening large table is usually used the "show features visible on map" option, but this is known to be bugged for postgis layers.</p> QGIS Application - Bug report #11631: field calculator update is very slowhttps://issues.qgis.org/issues/11631?journal_id=612902015-05-21T22:56:52ZGiovanni Manghigiovanni.manghi@gmail.com
<ul><li><strong>Resolution</strong> set to <i>worksforme</i></li><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Closed</i></li></ul><p>closing for lack of feedback.</p>