Loading a layer from a GPKG that contains a lot of other layers is very slow and makes the project very slow to navigate

[qgib]

Author Name: Giovanni Manghi (@gioman)
Original Redmine Issue: 16749
Affected QGIS version: 2.18.9
Redmine category:vectors

---

To replicate:

• download https://goo.gl/s1qJKa (very big): it has thousands of tables, this was made on purpose to make appear the problem in a very clear way (with a few hundreds tables the problem is already visible). The layers in this GPKG are a lot but are very small, tipically 1 feature per layer

• create the connection in DB manager, table list is slow to show but is expected, are a lot of tables

• try add the first layer/table to the project, very slow...

• try navigate the project, also very slow. Try add layers from other datasources and even disable the layer from the GPKG datasaource, stil very slow

• now download https://goo.gl/s37rzb : it contains only the first 3 tables/layers of the above one. Adding one layer from this other GPKG datasource is fast and there are no problem using it in the project.

• note that the Spatialite version of the above "big" GPKG datasource does not present the same issue > https://goo.gl/qJWeCt

• also notice that there are no issues with GPKG datasources with a "small" number of table/layers even if those are huge, millions of records.

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

• description was changed from To replicate:

• download https://goo.gl/s1qJKa (very big): it has thousands of tables, this was made on purpose to make appear the problem in a very clear way (with a few hundreds tables the problem is already visible). The layers in this GPKG are a lot but are very small, tipically 1 feature per layer

• create the connection in DB manager, table list is slow to show but is expected, are a lot of tables

• try add the first layer/table to the project, very slow...

• try navigate the project, also very slow. Try add layers from other datasources and even disable the layer from the GPKG datasaource, stil very slow

• now download https://goo.gl/s37rzb : it contains only the first 2 tables/layers of the above one. Adding one layer from this other GPKG datasource is fast and there are no problem using it in the project.

• note that the Spatialite version of the above "big" GPKG datasource does not present the same issue > https://goo.gl/qJWeCt

• also notice that there are no issues with GPKG datasources with a "small" number of table/layers eben if those are huge, millions of records. to To replicate:

• download https://goo.gl/s1qJKa (very big): it has thousands of tables, this was made on purpose to make appear the problem in a very clear way (with a few hundreds tables the problem is already visible). The layers in this GPKG are a lot but are very small, tipically 1 feature per layer

• create the connection in DB manager, table list is slow to show but is expected, are a lot of tables

• try add the first layer/table to the project, very slow...

• try navigate the project, also very slow. Try add layers from other datasources and even disable the layer from the GPKG datasaource, stil very slow

• now download https://goo.gl/s37rzb : it contains only the first 3 tables/layers of the above one. Adding one layer from this other GPKG datasource is fast and there are no problem using it in the project.

• note that the Spatialite version of the above "big" GPKG datasource does not present the same issue > https://goo.gl/qJWeCt

• also notice that there are no issues with GPKG datasources with a "small" number of table/layers even if those are huge, millions of records.

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

End of life notice: QGIS 2.18 LTR

Source:
http://blog.qgis.org/2019/03/09/end-of-life-notice-qgis-2-18-ltr/

QGIS 3.4 has recently become our new Long Term Release (LTR) version. This is a major step in our history – a long term release version based on the massive updates, library upgrades and improvements that we carried out in the course of the 2.x to 3x upgrade cycle.

We strongly encourage all users who are currently using QGIS 2.18 LTR as their preferred QGIS release to migrate to QGIS 3.4. This new LTR version will receive regular bugfixes for at least one year. It also includes hundreds of new functions, usability improvements, bugfixes, and other goodies. See the relevant changelogs for a good sampling of all the new features that have gone into version 3.4

Most plugins have been either migrated or incorporated into the core QGIS code base.

We strongly discourage the continued use of QGIS 2.18 LTR as it is now officially unsupported, which means we’ll not provide any bug fix releases for it.

You should also note that we intend to close all bug tickets referring to the now obsolete LTR version. Original reporters will receive a notification of the ticket closure and are encouraged to check whether the issue persists in the new LTR, in which case they should reopen the ticket.

If you would like to better understand the QGIS release roadmap, check out our roadmap page! It outlines the schedule for upcoming releases and will help you plan your deployment of QGIS into an operational environment.

The development of QGIS 3.4 LTR has been made possible by the work of hundreds of volunteers, by the investments of companies, professionals, and administrations, and by continuous donations and financial support from many of you. We sincerely thank you all and encourage you to collaborate and support the project even more, for the long term improvement and sustainability of the QGIS project.

---

• resolution was changed from to end of life
• status_id was changed from Open to Closed