Skip to content
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

Data-defined labeling takes 1560% longer to render #14819

Closed
qgib opened this issue Feb 18, 2012 · 9 comments
Closed

Data-defined labeling takes 1560% longer to render #14819

qgib opened this issue Feb 18, 2012 · 9 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Labeling Related to QGIS map labeling
Milestone

Comments

@qgib
Copy link
Contributor

qgib commented Feb 18, 2012

Author Name: Aren Cambre (Aren Cambre)
Original Redmine Issue: 5049
Affected QGIS version: master
Redmine category:labelling


For the attached SHP, here's how long it takes to render:

  • No labels: ~2.5 sec
  • Labels with field NAME and no data-defined setting: ~8.0 sec
  • Labels with field NAME and data-defined size set to POP_2000: ~41.6 sec

That's a 420% time increase over labeling with no data-defined setting and 1560% longer than no labeling at all.

Time was calculated with stopwatch, between pressing OK on the labeling dialog and when the map finally appears.



Related issue(s): #14818 (relates)
Redmine related issue(s): 5048


@qgib
Copy link
Contributor Author

qgib commented Feb 18, 2012

Author Name: Aren Cambre (Aren Cambre)


I ran this test on a laptop with 8 GB RAM (several GB free) and Intel Core i7 Q720 (1.6 GHz).

@qgib
Copy link
Contributor Author

qgib commented Feb 18, 2012

Author Name: Aren Cambre (Aren Cambre)


Related: #14818

@qgib
Copy link
Contributor Author

qgib commented Feb 21, 2012

Author Name: Marco Hugentobler (@mhugent)


This is because in POP_2000, there are huge values. If you set the font size e.g. to 1000 (points), you get long rendering times also if the size is not data-defined.
So the longer rendering is only because the labels are larger (over 1000000 points for Houston).

@qgib
Copy link
Contributor Author

qgib commented Feb 21, 2012

Author Name: Aren Cambre (Aren Cambre)


Ah, so looks like resolution of #14818 might be necessary to fix this performance issue?

@qgib
Copy link
Contributor Author

qgib commented Feb 21, 2012

Author Name: Jürgen Fischer (@jef-n)


Aren Cambre wrote:

Ah, so looks like resolution of #14818 might be necessary to fix this performance issue?

or by using an attribute that is usable as size - eg. by using the field calculator to produce a appropriately scaled value in an additional attribute.

@qgib
Copy link
Contributor Author

qgib commented Sep 4, 2012

Author Name: Paolo Cavallini (@pcav)


  • fixed_version_id was configured as Version 2.0.0

@qgib
Copy link
Contributor Author

qgib commented May 13, 2013

Author Name: Nyall Dawson (@nyalldawson)


This might be closable now -- this can be achieved by using an expression for the definition and using the new "scale_linear" function.


  • status_id was changed from Open to Feedback

@qgib
Copy link
Contributor Author

qgib commented May 29, 2013

Author Name: Larry Shaffer (Larry Shaffer)


Should be fixed with commit 45f374f

Reopen if necessary


  • status_id was changed from Feedback to Resolved
  • resolution was changed from to fixed

@qgib
Copy link
Contributor Author

qgib commented Feb 13, 2014

Author Name: Jürgen Fischer (@jef-n)


  • status_id was changed from Resolved to Closed

@qgib qgib added Bug Either a bug report, or a bug fix. Let's hope for the latter! Labeling Related to QGIS map labeling labels May 24, 2019
@qgib qgib added this to the Version 2.0.0 milestone May 24, 2019
@qgib qgib closed this as completed May 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Labeling Related to QGIS map labeling
Projects
None yet
Development

No branches or pull requests

1 participant