You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On the test server tilekiln was killed while generating z13. It could have been something else using the memory, but that seems unlikely since it wasn't getting killed earlier.
Rendering 67108864 tiles over 8 threads
36%|███████████████████████████████████████████████████████ | 23862146/67108864 [1:48:20<18:52:14, 636.59it/s]
Process ForkPoolWorker-2:
Process ForkPoolWorker-7:
Process ForkPoolWorker-4:
Process ForkPoolWorker-3:
Process ForkPoolWorker-6:
Process ForkPoolWorker-1:
Killed
Process ForkPoolWorker-8:
Traceback (most recent call last):
tilekiln has total_vm=5gb rss=3.6gb pgtables_bytes=41gb for the top process, while the others each have about total_vm=.8gb rss=tiny pgtables_bytes=6.5gb
The text was updated successfully, but these errors were encountered:
Note: This was done by feeding the list of all z13 tiles into tilekiln as the entire zoom function is not yet coded. I should see if it's still an issue after that, because that's the correct way to generate a high zoom
On the test server tilekiln was killed while generating z13. It could have been something else using the memory, but that seems unlikely since it wasn't getting killed earlier.
dmesg reports
From the log the tilekiln/postgres jobs at the bottom were the generation run.
tilekiln has total_vm=5gb rss=3.6gb pgtables_bytes=41gb for the top process, while the others each have about total_vm=.8gb rss=tiny pgtables_bytes=6.5gb
The text was updated successfully, but these errors were encountered: