20,741
edits
Canvas development: Difference between revisions
Jump to navigation
Jump to search
→Property I/O observations
| Line 481: | Line 481: | ||
=== Property I/O observations === | === Property I/O observations === | ||
Speaking for the Shuttle, that (performance problems/lag) has very little to do with canvas as such. There are 11 MDUs on the Shuttle flightdeck, and the way the Shuttle avionics works, they typically display close to a hundred values each, so that's of the order of ~1000 different parameters that need to be simulated, fetched and displayed _per update cycle_ (and yeah, most parameters you see are really simulated and not just unchanging text).<ref>{{cite web | |||
|url = https://sourceforge.net/p/flightgear/mailman/message/35925540/ | |||
|title = <nowiki> Re: [Flightgear-devel] RFD: FlightGear and the changing state of | |||
air navigation </nowiki> | |||
|author = <nowiki> Thorsten Renk </nowiki> | |||
|date = Jul 3rd, 2017 | |||
|added = Jul 3rd, 2017 | |||
|script_version = 0.40 | |||
}}</ref> | |||
actual problem is property I/O - we can't read/write several hundreds of properties per frame without creating a bottleneck. So it's largely irrelevant how fast the Nasal code runs, whether it's parallel or whether it's Python-driven code running on the GPU - as long as property I/O speed doesn't change, performance will be stuck right there.<ref>{{cite web | actual problem is property I/O - we can't read/write several hundreds of properties per frame without creating a bottleneck. So it's largely irrelevant how fast the Nasal code runs, whether it's parallel or whether it's Python-driven code running on the GPU - as long as property I/O speed doesn't change, performance will be stuck right there.<ref>{{cite web | ||
|url = https://forum.flightgear.org/viewtopic.php?p=296410#p296410 | |url = https://forum.flightgear.org/viewtopic.php?p=296410#p296410 | ||