1,746
edits
Osm2city worldbuild: Difference between revisions
Jump to navigation
Jump to search
Add some info on the 1st LTS rollout, link to dedicated info and tips page, so people don't get confused in future with different info/tips related to later improved rollouts of OSM2City.
m (+cat: Custom scenery) |
(Add some info on the 1st LTS rollout, link to dedicated info and tips page, so people don't get confused in future with different info/tips related to later improved rollouts of OSM2City.) |
||
| Line 1: | Line 1: | ||
{{lowercase title}} | {{lowercase title}} | ||
The '''osm2city worldbuild''' is an attempt by merspieler started in May 2019 of providing global coverage with osm2city scenery. | The '''osm2city worldbuild''' is an attempt by merspieler started in May 2019 of providing global coverage with osm2city scenery. The 1st worldbuild has been completed. | ||
== Machine == | == Machine == | ||
| Line 9: | Line 9: | ||
For storage I've started with five 4TB HDDs configured in a RAIDZ2 with an effective capacity of just below 12TB but changed to RAID10 (with one spare drive, about 8TB effective) to improve IO performance. Currently 8TB this is more than is needed. | For storage I've started with five 4TB HDDs configured in a RAIDZ2 with an effective capacity of just below 12TB but changed to RAID10 (with one spare drive, about 8TB effective) to improve IO performance. Currently 8TB this is more than is needed. | ||
As of writing the global osm data in the database has a size of 2.3TB but this requirement can be lowered (with a penalty in runtime) by only importing the required area from the highly compressed .osm.pbf file. With this approach, the initial try worked relativly well on a 1TB HDD with enough headroom. There are quite a number of random IOPS which causes some IO wait time, up to 80% of the CPU on my Server so an SSD would certainly benificial for some of the data or as L2ARC. | As of writing the global osm data in the database has a size of 2.3TB but this requirement can be lowered (with a penalty in runtime) by only importing the required area from the highly compressed .osm.pbf file. With this approach, the initial try worked relativly well on a 1TB HDD with enough headroom. There are quite a number of random IOPS which causes some IO wait time, up to 80% of the CPU on my Server so an SSD would certainly benificial for some of the data or as L2ARC. | ||
== Rollouts on LTS == | |||
''See [[OSM2City 1st Worldbuild|'''information and performance tips for the OSM2City 1st worldbuild''']] .'' | |||
The 1st rollout on the FlightGear [[Release Plan|Long Term Stable]] (LTS) stream was in [[Changelog 2020.3|FlightGear 2020.3.7]] point release. FlightGear 2020.3.7 LTS will automatically download from [[TerraSync]]. FlightGear 2020.3.6 and earlier will not automatically download OSM2City data. A small amount of existing OSM2City data in an old format was removed. | |||
[[Category:Osm2city]] | [[Category:Osm2city]] | ||
[[Category:Custom scenery]] | [[Category:Custom scenery]] | ||