Hi, Following on from the navcache, I have a couple more changes planned to further improve our *perceived* startup time. This mostly means either caching data which is expensive to parse, or much better, delaying it until it's actually needed, as I already did for the HUD and AI-traffic files.
The current hot-spots are the joystick code (parses every XML file in Input/ each time, it seems), Nasal and loading the actual aircraft model. The joystick code is not that bad, but it would be fairly easy to time-stamp the XML files and cache the name -> config file mapping in the cache. Nasal loading takes a few seconds, but given what we do in Nasal I'm not especially worried by this. Making some ancillary Nasal files be loaded later would help, but this requires some knowledge of which Nasal might be needed during scenery loading - which we don't currently have. The big gain is to run aircraft loading in parallel with the scenery load - which is also a fairly simple change I think, but may expose threading bugs in Simgear. So that's what I will attempt in the next few days. (We'd still wait on both scenery *and* the aircraft model being loaded, before initing the FDM and fading the splash-screen, so there shouldn't be any user-visible change except faster startup, I hope) James ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
