[Tile-serving] [osm2pgsql-dev/osm2pgsql] Daylight Ingest and Slow Deletions (Discussion #2088)

[mboeringa]

@pyoung-sc , apart from possible latency issues as Paul hinted on, I do think the current recommendations especially for `work_mem` (50MB) are still very conservative in the manual, even taking into account the 64GB RAM limit that is presumed there. They definitely do not represent recommended settings for a machine with 256GB, like you seem to have been using last.

My current postgresql settings on a  512GB machine (actually only 420GB assigned to the VM, + another 100GB SWAP!!! - _you need the latter!_), are visible in [this benchmark](https://wiki.openstreetmap.org/wiki/Osm2pgsql/benchmarks#Planet_(75.1GB_PBF,_2023-07-17)_on_HP_Z840_workstation,_512GB_DDR4_2133,_2x_Xeon_E5-2699v4_22C,_5x_Samsung_970_EVO_Plus_2TB_NVMe_RAID_0,_4x_Intel_OPTANE_P1600X_110GB_NVMe_RAID_0,_Ubuntu_22.04_(flex_|_--slim)_~8h)

As you can see, I have `work_mem` in the **GB** set, not MB. Also note that one of biggest gains in general is turning `synchronous_commit=off`. If your workflow allows at least temporarily switching it off, I recommend it.



-- 
Reply to this email directly or view it on GitHub:
https://github.com/osm2pgsql-dev/osm2pgsql/discussions/2088#discussioncomment-7409889
You are receiving this because you are subscribed to this thread.

Message ID: <osm2pgsql-dev/osm2pgsql/repo-discussions/2088/comments/7409889 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tile-serving/attachments/20231028/1e884e51/attachment.htm>