When processing an Antarctica extract, CPU is sitting at around 120% on a 16-core machine during much of tile writing.
This suggests we have a lock issue of some sort - either one of our own mutexs or sqlite. Antarctica is characterised by large areas of emptyish tiles so there’s less geometry processing going on than usual.
We could consider batching sqlite inserts if this proves to be the cause.
598 has made this significantly better. Rather than sitting at 120%, it's now closer to 280% or so. I'll leave this open in case any other improvements come to mind but I think we've probably plucked the low-hanging sqlite fruit.
systemed
commented
9 months ago
When processing an Antarctica extract, CPU is sitting at around 120% on a 16-core machine during much of tile writing.
This suggests we have a lock issue of some sort - either one of our own mutexs or sqlite. Antarctica is characterised by large areas of emptyish tiles so there’s less geometry processing going on than usual.
We could consider batching sqlite inserts if this proves to be the cause.