20,741
edits
TerraGear scenery build server: Difference between revisions
Jump to navigation
Jump to search
TerraGear scenery build server (view source)
Revision as of 13:30, 3 December 2015
, 3 December 2015→BOINC
(→BOINC) |
(→BOINC) |
||
| Line 236: | Line 236: | ||
== BOINC == | == BOINC == | ||
{{DeQuote}} | |||
{{FGCquote | |||
|1= For what it's worth, the primary bottleneck for scenery generation is disk I/O -- reading and writing files. There is a computational aspect, but on the whole it's disk IO that will limit things. | |||
Back in the day when I was cranking out the world scenery myself, I had a cluster of linux machines running in parallel -- all talking to an nfs server -- I thought it was a pretty slick setup at the time, but I'm sure a fast single modern PC could outperform the cluster of 20-25 PC's I was using at the time. | |||
|2= {{cite web | |||
| url = http://forum.flightgear.org/viewtopic.php?p=144405#p144405 | |||
| title = <nowiki>Re: Create a </nowiki> | |||
| author = <nowiki>curt</nowiki> | |||
| date = Dec 9th, 2011 | |||
| added = Dec 9th, 2011 | |||
| script_version = 0.23 | |||
}} | |||
}} | |||
{{FGCquote | {{FGCquote | ||
|1= I understand that generating the scenery from the raw data takes quite some CPU time. | |1= I understand that generating the scenery from the raw data takes quite some CPU time. | ||
| Line 268: | Line 283: | ||
| date = Dec 3rd, 2015 | | date = Dec 3rd, 2015 | ||
| added = Dec 3rd, 2015 | | added = Dec 3rd, 2015 | ||
| script_version = 0.23 | |||
}} | |||
}} | |||
{{FGCquote | |||
|1= we could adopt an even simpler approach: | |||
<ol style="list-style-type: decimal"># improve the existing tools (and add new ones) to support regenerating a single tile without depending on the surrounding ones; | |||
# expand the FlightGear Scenery Database webforms, if needed, to allow any FG user to submit improvements that can not be done via the Airport Gateway or OSM; | |||
# periodically grab all improvements from OSM/the Airport Gateway via their APIs; | |||
# regenerate the single tiles using a distributed system like BOINC (see [[TerraGear scenery build server|this page on the wiki]]); | |||
# publish the scenery via HTTP (from a single website or a network of mirrors). | |||
|2= {{cite web | |||
| url = http://forum.flightgear.org/viewtopic.php?p=236906#p236906 | |||
| title = <nowiki>Re: Google code colse there doors</nowiki> | |||
| author = <nowiki>elgaton</nowiki> | |||
| date = Mar 26th, 2015 | |||
| added = Mar 26th, 2015 | |||
| script_version = 0.23 | |||
}} | |||
}} | |||
{{FGCquote | |||
|1= I thought of a ready to use vm that contains the necessary tools (terragear) + a python script that connects to a server, downloads the needed data / scripts and starts compiling the scenery. | |||
After the task is done the data would be uploaded back to the server. | |||
The server could run a python script too, that manages the connected compile slaves. The script could take the compile slave capabilities (disk io, processors, line bandwidth) into account and assign tasks based on this to the slave. | |||
|2= {{cite web | |||
| url = http://forum.flightgear.org/viewtopic.php?p=144459#p144459 | |||
| title = <nowiki>Re: Create a </nowiki> | |||
| author = <nowiki>ot-666</nowiki> | |||
| date = Dec 10th, 2011 | |||
| added = Dec 10th, 2011 | |||
| script_version = 0.23 | | script_version = 0.23 | ||
}} | }} | ||