Geodjango spatialite test database initialization very slow on some systems
|Reported by:||Owned by:||Doug Goldstein|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
While testing some of my gis models, I noticed that the test database setup ran really slowly (about 16 minutes on my harddisk).
I dug a little bit deeper into the code and noticed that the execution of load_spatialite_sql() in contrib/gis/db/spatialite/creation.py went really slowly. To be more precise the line:
I found this issue here:
This basically says that the InitSpatialMetaData() command is really slow on some systems, because it executes in many transactions.
One could speed it up by using one of the following solutions:
- pass 1 to the function. This makes (at least recent versions of spatialite) it execute in a single transaction. I am not really sure for which versions of spatialite this works.
- manually control the transaction:
cur.execute("BEGIN ;") cur.execute("SELECT InitSpatialMetaData()") cur.execute("COMMIT ;")
For people who have the test database outside the memory this might be a huge problem.
Change History (6)
comment:1 Changed 2 years ago by
|Patch needs improvement:||unset|
|Triage Stage:||Unreviewed → Accepted|
|Type:||Bug → Cleanup/optimization|
|Version:||1.7-rc-2 → master|
comment:3 Changed 2 years ago by
|Owner:||changed from nobody to Doug Goldstein|
|Status:||new → assigned|