Replies: 2 comments
-
I looked into this and you are right, we could release cache memory earlier. I have no idea how much this will actually improve performance, because the memory is unused and so it should eventually be purged from memory anyway. But it should be fixed in any case. I have some code changes, but they need more tests. |
Beta Was this translation helpful? Give feedback.
0 replies
-
See also my issue: #1532 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
It seems that the memory used by the cache is released late during an osm2pgsql import process.
Once the PG tables are created, I don't think the cache is needed anymore, and the RAM used cannot be used by PG and other caches during the clustering/index creation.
I'm currently finishing a full planet import, and osm2pgsql still uses 65GB of RAM (I allocated 70G for the cache) while line/polygon are creating their index.
Beta Was this translation helpful? Give feedback.
All reactions