Bug report #18293

New node tool is really slow to index for big project with many editable layers

Added by Regis Haubourg over 2 years ago. Updated almost 2 years ago.

Status:Closed
Priority:High
Assignee:-
Category:Digitising
Affected QGIS version:3.0.0 Regression?:No
Operating System: Easy fix?:No
Pull Request or Patch supplied:No Resolution:fixed/implemented
Crashes QGIS or corrupts data:No Copied to github as #:26184

Description

Using a project with transaction groups option activated, I takes several minutes to be able to create the snapping index cache.

I think that we need options to manage the snapping index coverage.

It could be:

- all editable layers
- only active layer

and maybe also
- only snappable layers

That option would suit well into the snapping option panel, together with a default setting in the general option (digitising tab)

Régis

History

#1 Updated by Martin Dobias over 2 years ago

What if the transaction groups are not enabled - is it still slow?

Might be useful to try changing the indexing strategy to see if there is a difference - in python console run this:

iface.mapCanvas().snappingUtils().setIndexingStrategy(QgsSnappingUtils.IndexExtent)

Also, right now the index preparation is always sequential - running it in parallel for multiple layers may also speed it up significantly.

#2 Updated by Giovanni Manghi over 2 years ago

  • Status changed from Open to Feedback

#3 Updated by Regis Haubourg almost 2 years ago

  • Resolution set to fixed/implemented
  • Status changed from Feedback to Closed

Tested in latest master 3.3, and it's fast fast! happy me.

Also available in: Atom PDF