New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extremely slower time to open attribute table in 2.18.7 compared to 2.14.14 #24479
Comments
Author Name: Alessandro Pasotti (@elpaso) Is that a point release build or a particular commit? |
Author Name: Jürgen Fischer (@jef-n)
https://issues.qgis.org/issues/16239 and/or https://issues.qgis.org/issues/15752 I have tested a 758719 polygon features on 2.18.7 (no debug output) and to open the table it takes over 6 minutes! Can provide the dataset. Rendering time is very similar. to This could be related to #24149 and/or #23674 I have tested a 758719 polygon features on 2.18.7 (no debug output) and to open the table it takes over 6 minutes! Can provide the dataset. Rendering time is very similar. |
Author Name: Jürgen Fischer (@jef-n)
|
Author Name: Jürgen Fischer (@jef-n)
|
Author Name: Giovanni Manghi (@gioman) Alessandro Pasotti wrote:
qgis 2.14.14 and 2.18.7 as installed by a normal user from osgeo4w under a clean Windows 7 environment. Same observation on Ubuntu Linux from qgis repositories (the ones using also ubuntugis). |
Author Name: Giovanni Manghi (@gioman) see also: https://lists.osgeo.org/pipermail/qgis-psc/2017-May/005258.html |
Author Name: Nyall Dawson (@nyalldawson) A bunch of fixes have been implemented in master and 2.18 which restore the performance to 2.14.0 levels
|
Author Name: Giovanni Manghi (@gioman)
Original Redmine Issue: 16577
Affected QGIS version: 2.18.7
Redmine category:attribute_table
This could be related to #24149 and/or #23674
I have tested a 758719 polygon features on 2.18.7 (no debug output) and to open the table it takes over 6 minutes!
The same table on 2.14.14 (no debug output) open in a few seconds.
Can provide the dataset.
Rendering time is very similar.
Related issue(s): #23674 (relates), #24149 (relates)
Redmine related issue(s): 15752, 16239
The text was updated successfully, but these errors were encountered: