Re: [Flightgear-devel] FlightGear startup time
Harald JOHNSEN wrote: Another problem not related to pure performance is that the first retrieval of metar data can block FG for a long time (perhaps one minute) when the metar server is not accessible (or when there is any network problem). The code does a lot of (useless) retries. Perhaps its simpler not to update the metar on IO error and continue silently. I have noticed this too. We are doing the metar fetching in a separate thread to avoid this specific problem, but I wonder if something in that process has broke, or if some how the metar thread can still manage to block the main thread while it is out fetching data. I haven't had time to poke around with this myself, but it would be worth trying to come up with a way to reproduce the problem so one of the developers could poke around and try to figure out what is going on. Thread code is tricky and there could be a subtle blocking bug in there some place. Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
40 seconds for CVS vesion on Dell (laptop) running Linux Fedora Core 2, 1.6 GHz processor, 2 GB RAM. I can live with that. Mike --- Frederic Bouvier <[EMAIL PROTECTED]> wrote: > It takes 23 seconds to start my build on an amd64 > 3400, 1Gb ram. > > -Fred > > Drew a écrit : > > >I'm compiling a Release build. It takes me a bit > under a minute to > >bring it up, which isn't as bad as the 5 minutes > Vivian reported, but > >it's still longer than I'd like (and longer than I > believe is > >necessary). I'll see what I can do about disabling > navaids...that > >seems like it be a lot of help. I haven't found a > property in > >preferences.xml or a command-line option for this, > yet. > > > >Drew > > > >On 5/24/05, Frederic Bouvier <[EMAIL PROTECTED]> > wrote: > > > > > >>Drew a écrit : > >> > >> > >> > >>>FlightGear takes nearly a minute to start up from > my Windows build, > >>>and I'm just wondering if there's an easy way to > shorten this if I'm > >>>not using all of flightgear's features. Is there > one particular task > >>>that takes particularly long? > >>> > >>> > >>> > >>> > >>Do you use the Debug or the Release build ? > >>MSVC 7.x adds a lot of debug code in memory > management (assertion check, > >>corrupted heap) that makes the Debug build > **very** slow. > >>The Release build, as in the official win32 > releases, is way faster. > >>Maybe 5x to 10x. > >> > >>-Fred > >> > >> > > > > ___ > Flightgear-devel mailing list > Flightgear-devel@flightgear.org > http://mail.flightgear.org/mailman/listinfo/flightgear-devel > 2f585eeea02e2c79d7b1d8c4963bae2d > __ Yahoo! Mail Stay connected, organized, and protected. Take the tour: http://tour.mail.yahoo.com/mailtour.html ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
Drew a écrit : Correction, that was pthreadVC-nd.dll As I said, you must install fgsetup-0.9.8a.exe before, and replace fgfs.exe -Fred ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
Success! I just commented out the call to fgAirportDBLoad as well, and now it starts up in less than 20 seconds, which is perfect. It seems to run more smoothly as well having freed up so much memory, but I can't confirm that. KSFO still seems to be there, visually, and all I need from flightgear are the visual model and terrain elevations. Am I losing anything important by bypassing this? Is the airport data simply marker beacon and ILS information? Drew On 5/24/05, Drew <[EMAIL PROTECTED]> wrote: > That's helpful...thanks. I just commented the call to FGNavDBInit, > which shaved off about 10 seconds, so that's some good progress...I'll > play with it some more to see what I can do. > > Thanks for all your help. > > On 5/24/05, Frederic Bouvier <[EMAIL PROTECTED]> wrote: > > Frederic Bouvier a écrit : > > > > > It takes 23 seconds to start my build on an amd64 3400, 1Gb ram. > > > > > > 9 seconds to load airports and nav data, > > 5 seconds to init other subsystems, > > 9 seconds to load scenery objects. > > > > -Fred > > > > > > > > ___ > > Flightgear-devel mailing list > > Flightgear-devel@flightgear.org > > http://mail.flightgear.org/mailman/listinfo/flightgear-devel > > 2f585eeea02e2c79d7b1d8c4963bae2d > > > ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
Correction, that was pthreadVC-nd.dll On 5/24/05, Drew <[EMAIL PROTECTED]> wrote: > I will, probably tonight...I tried it really quickly, and it needs a > C-nd.dll. I suspect there are similar issues, so I'll work through it > when I've got some more time. > > Thanks again, > Drew > > On 5/24/05, Frederic Bouvier <[EMAIL PROTECTED]> wrote: > > Drew a écrit : > > > > >Really? That's helpful. I wasn't able to get the CVS software to > > >work last time I tried...it seems like that's a useful feature, so I > > >think I'll try again. > > > > > > > > Get a taste of it by downloading the binary I posted earlier. > > > > -Fred > > > > > > > > ___ > > Flightgear-devel mailing list > > Flightgear-devel@flightgear.org > > http://mail.flightgear.org/mailman/listinfo/flightgear-devel > > 2f585eeea02e2c79d7b1d8c4963bae2d > > > ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
I will, probably tonight...I tried it really quickly, and it needs a C-nd.dll. I suspect there are similar issues, so I'll work through it when I've got some more time. Thanks again, Drew On 5/24/05, Frederic Bouvier <[EMAIL PROTECTED]> wrote: > Drew a écrit : > > >Really? That's helpful. I wasn't able to get the CVS software to > >work last time I tried...it seems like that's a useful feature, so I > >think I'll try again. > > > > > Get a taste of it by downloading the binary I posted earlier. > > -Fred > > > > ___ > Flightgear-devel mailing list > Flightgear-devel@flightgear.org > http://mail.flightgear.org/mailman/listinfo/flightgear-devel > 2f585eeea02e2c79d7b1d8c4963bae2d > ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
Drew a écrit : Really? That's helpful. I wasn't able to get the CVS software to work last time I tried...it seems like that's a useful feature, so I think I'll try again. Get a taste of it by downloading the binary I posted earlier. -Fred ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
Really? That's helpful. I wasn't able to get the CVS software to work last time I tried...it seems like that's a useful feature, so I think I'll try again. Drew On 5/24/05, Frederic Bouvier <[EMAIL PROTECTED]> wrote: > Do you compile the last code ? > Now the splash screen writes the current stage on screen and it is > easier to know where time is spent. > > -Fred > > Drew a écrit : > > >That's helpful...thanks. I just commented the call to FGNavDBInit, > >which shaved off about 10 seconds, so that's some good progress...I'll > >play with it some more to see what I can do. > > > >Thanks for all your help. > > > >On 5/24/05, Frederic Bouvier <[EMAIL PROTECTED]> wrote: > > > > > >>Frederic Bouvier a écrit : > >> > >> > >> > >>>It takes 23 seconds to start my build on an amd64 3400, 1Gb ram. > >>> > >>> > >>9 seconds to load airports and nav data, > >>5 seconds to init other subsystems, > >>9 seconds to load scenery objects. > >> > >>-Fred > >> > >> > > > ___ > Flightgear-devel mailing list > Flightgear-devel@flightgear.org > http://mail.flightgear.org/mailman/listinfo/flightgear-devel > 2f585eeea02e2c79d7b1d8c4963bae2d > ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
Do you compile the last code ? Now the splash screen writes the current stage on screen and it is easier to know where time is spent. -Fred Drew a écrit : That's helpful...thanks. I just commented the call to FGNavDBInit, which shaved off about 10 seconds, so that's some good progress...I'll play with it some more to see what I can do. Thanks for all your help. On 5/24/05, Frederic Bouvier <[EMAIL PROTECTED]> wrote: Frederic Bouvier a écrit : It takes 23 seconds to start my build on an amd64 3400, 1Gb ram. 9 seconds to load airports and nav data, 5 seconds to init other subsystems, 9 seconds to load scenery objects. -Fred ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
That's helpful...thanks. I just commented the call to FGNavDBInit, which shaved off about 10 seconds, so that's some good progress...I'll play with it some more to see what I can do. Thanks for all your help. On 5/24/05, Frederic Bouvier <[EMAIL PROTECTED]> wrote: > Frederic Bouvier a écrit : > > > It takes 23 seconds to start my build on an amd64 3400, 1Gb ram. > > > 9 seconds to load airports and nav data, > 5 seconds to init other subsystems, > 9 seconds to load scenery objects. > > -Fred > > > > ___ > Flightgear-devel mailing list > Flightgear-devel@flightgear.org > http://mail.flightgear.org/mailman/listinfo/flightgear-devel > 2f585eeea02e2c79d7b1d8c4963bae2d > ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
Drew, The question was intended to the other Linux adopters, not you specifically. -Fred Drew a écrit : I don't know. I can't try it, though, because this is a work computer, and 'm not supposed to install Linux. On 5/24/05, Frederic Bouvier wrote: Drew a écrit : That's probably about right, but your computer is much more capable than mine (Intel Pentium M 1600 MHz laptop, 512 Megs of RAM). I just timed mine at 57 seconds. On 5/24/05, Frederic Bouvier wrote: It takes 23 seconds to start my build on an amd64 3400, 1Gb ram. Is it different under Linux ? -Fred ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
Frederic Bouvier wrote: > By popular demand ( sort of ;), I uploaded my current release build ( > latest CVS ) here : Thanks ;-) Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
Frederic Bouvier a écrit : It takes 23 seconds to start my build on an amd64 3400, 1Gb ram. 9 seconds to load airports and nav data, 5 seconds to init other subsystems, 9 seconds to load scenery objects. -Fred ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
I don't know. I can't try it, though, because this is a work computer, and 'm not supposed to install Linux. On 5/24/05, Frederic Bouvier <[EMAIL PROTECTED]> wrote: > Drew a écrit : > > >That's probably about right, but your computer is much more capable > >than mine (Intel Pentium M 1600 MHz laptop, 512 Megs of RAM). I just > >timed mine at 57 seconds. > > > >On 5/24/05, Frederic Bouvier wrote: > > > > > >>It takes 23 seconds to start my build on an amd64 3400, 1Gb ram. > >> > >> > > Is it different under Linux ? > > -Fred > > > > ___ > Flightgear-devel mailing list > Flightgear-devel@flightgear.org > http://mail.flightgear.org/mailman/listinfo/flightgear-devel > 2f585eeea02e2c79d7b1d8c4963bae2d > ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
Drew a écrit : That's probably about right, but your computer is much more capable than mine (Intel Pentium M 1600 MHz laptop, 512 Megs of RAM). I just timed mine at 57 seconds. On 5/24/05, Frederic Bouvier wrote: It takes 23 seconds to start my build on an amd64 3400, 1Gb ram. Is it different under Linux ? -Fred ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
Martin Spott wrote : In article <[EMAIL PROTECTED]> you wrote: The Release build, as in the official win32 releases, is way faster. Maybe 5x to 10x. BTW, Frederic, would you consider uploading a Win32 binary - to the 'well-known site' - that represents the current stae of development ? By popular demand ( sort of ;), I uploaded my current release build ( latest CVS ) here : ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/fgfs-win32-20050524.zip It goes on top of a valid install, as it requires some dlls not provided here, after the usual backup, of course. -Fred ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
That's probably about right, but your computer is much more capable than mine (Intel Pentium M 1600 MHz laptop, 512 Megs of RAM). I just timed mine at 57 seconds. On 5/24/05, Frederic Bouvier <[EMAIL PROTECTED]> wrote: > It takes 23 seconds to start my build on an amd64 3400, 1Gb ram. > > -Fred > > Drew a écrit : > > >I'm compiling a Release build. It takes me a bit under a minute to > >bring it up, which isn't as bad as the 5 minutes Vivian reported, but > >it's still longer than I'd like (and longer than I believe is > >necessary). I'll see what I can do about disabling navaids...that > >seems like it be a lot of help. I haven't found a property in > >preferences.xml or a command-line option for this, yet. > > > >Drew > > > >On 5/24/05, Frederic Bouvier <[EMAIL PROTECTED]> wrote: > > > > > >>Drew a écrit : > >> > >> > >> > >>>FlightGear takes nearly a minute to start up from my Windows build, > >>>and I'm just wondering if there's an easy way to shorten this if I'm > >>>not using all of flightgear's features. Is there one particular task > >>>that takes particularly long? > >>> > >>> > >>> > >>> > >>Do you use the Debug or the Release build ? > >>MSVC 7.x adds a lot of debug code in memory management (assertion check, > >>corrupted heap) that makes the Debug build **very** slow. > >>The Release build, as in the official win32 releases, is way faster. > >>Maybe 5x to 10x. > >> > >>-Fred > >> > >> > > > > ___ > Flightgear-devel mailing list > Flightgear-devel@flightgear.org > http://mail.flightgear.org/mailman/listinfo/flightgear-devel > 2f585eeea02e2c79d7b1d8c4963bae2d > ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
It takes 23 seconds to start my build on an amd64 3400, 1Gb ram. -Fred Drew a écrit : I'm compiling a Release build. It takes me a bit under a minute to bring it up, which isn't as bad as the 5 minutes Vivian reported, but it's still longer than I'd like (and longer than I believe is necessary). I'll see what I can do about disabling navaids...that seems like it be a lot of help. I haven't found a property in preferences.xml or a command-line option for this, yet. Drew On 5/24/05, Frederic Bouvier <[EMAIL PROTECTED]> wrote: Drew a écrit : FlightGear takes nearly a minute to start up from my Windows build, and I'm just wondering if there's an easy way to shorten this if I'm not using all of flightgear's features. Is there one particular task that takes particularly long? Do you use the Debug or the Release build ? MSVC 7.x adds a lot of debug code in memory management (assertion check, corrupted heap) that makes the Debug build **very** slow. The Release build, as in the official win32 releases, is way faster. Maybe 5x to 10x. -Fred ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
Harald JOHNSEN wrote: I've just looked at the code. I see that the error count is incremented in the catch but I think I don't enter here, I am spamed with 'metar data too old' on the console. After some time I have a real socket error and I think that after that I enter the catch statement and the error counter is finaly incremented ! Strange that the increment is inside the #ifdef threads. So to be clear : 1) I have a lot of 'metar too old' message (no log file but its more than 50 per loop) 2) after some time I have a sigio (if I remember well, that does not happens everyday of course) 3) repeat 3 times Its with cvs version and that happens in the init code. I see, the problem is basically introduced again after adding code to see whether the data is too old. This probably requires another error counter ... Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
I'm compiling a Release build. It takes me a bit under a minute to bring it up, which isn't as bad as the 5 minutes Vivian reported, but it's still longer than I'd like (and longer than I believe is necessary). I'll see what I can do about disabling navaids...that seems like it be a lot of help. I haven't found a property in preferences.xml or a command-line option for this, yet. Drew On 5/24/05, Frederic Bouvier <[EMAIL PROTECTED]> wrote: > Drew a écrit : > > >FlightGear takes nearly a minute to start up from my Windows build, > >and I'm just wondering if there's an easy way to shorten this if I'm > >not using all of flightgear's features. Is there one particular task > >that takes particularly long? > > > > > > Do you use the Debug or the Release build ? > MSVC 7.x adds a lot of debug code in memory management (assertion check, > corrupted heap) that makes the Debug build **very** slow. > The Release build, as in the official win32 releases, is way faster. > Maybe 5x to 10x. > > -Fred > > > > ___ > Flightgear-devel mailing list > Flightgear-devel@flightgear.org > http://mail.flightgear.org/mailman/listinfo/flightgear-devel > 2f585eeea02e2c79d7b1d8c4963bae2d > ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
Drew a écrit : FlightGear takes nearly a minute to start up from my Windows build, and I'm just wondering if there's an easy way to shorten this if I'm not using all of flightgear's features. Is there one particular task that takes particularly long? Do you use the Debug or the Release build ? MSVC 7.x adds a lot of debug code in memory management (assertion check, corrupted heap) that makes the Debug build **very** slow. The Release build, as in the official win32 releases, is way faster. Maybe 5x to 10x. -Fred ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
Erik Hofman wrote: Harald JOHNSEN wrote: Another problem not related to pure performance is that the first retrieval of metar data can block FG for a long time (perhaps one minute) when the metar server is not accessible (or when there is any network problem). The code does a lot of (useless) retries. Perhaps its simpler not to update the metar on IO error and continue silently. Which version of FlightGear are you using? This has been fixed a long time ago. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d I've just looked at the code. I see that the error count is incremented in the catch but I think I don't enter here, I am spamed with 'metar data too old' on the console. After some time I have a real socket error and I think that after that I enter the catch statement and the error counter is finaly incremented ! Strange that the increment is inside the #ifdef threads. So to be clear : 1) I have a lot of 'metar too old' message (no log file but its more than 50 per loop) 2) after some time I have a sigio (if I remember well, that does not happens everyday of course) 3) repeat 3 times Its with cvs version and that happens in the init code. Harald. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
On Tuesday 24 May 2005 16:09, Harald JOHNSEN wrote: > Edit apt.dat and runways.dat, just leave KSFO for example. Normaly you > should leave a few others used in ai or atc (I don't remember) or > disable this functionalities if you don't want an abort of FG. > The latest version of the Traffic manager derived AI is done such that it discards any route that tries to fly to/from an unknown airport. Unfortunately this has to be done at startup, adding to the initialization time. The run-time consequence if you only keep one airport is that you won't see any airliner traffic... Cheers, Durk ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
Le mardi 24 mai 2005 à 16:43 +0200, Erik Hofman a écrit : > Harald JOHNSEN wrote: > > > Another problem not related to pure performance is that the first > > retrieval of metar data can block FG for a long time (perhaps one > > minute) when the metar server is not accessible (or when there is any > > network problem). The code does a lot of (useless) retries. Perhaps its > > simpler not to update the metar on IO error and continue silently. > > Which version of FlightGear are you using? > This has been fixed a long time ago. > On my side I do confirm: Metar is waiting for an answer during startup. I do use permanently Metar , if the network is off, fgfs wait for a lot of time before going on ===> fgfs 9.8 and fgfs cvs > -- Gerard ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
Hi Erik: The version is v0.9.8 for windows. Clifford From: Erik Hofman <[EMAIL PROTECTED]> Reply-To: FlightGear developers discussions To: FlightGear developers discussions Subject: Re: [Flightgear-devel] FlightGear startup time Date: Tue, 24 May 2005 16:43:32 +0200 Harald JOHNSEN wrote: Another problem not related to pure performance is that the first retrieval of metar data can block FG for a long time (perhaps one minute) when the metar server is not accessible (or when there is any network problem). The code does a lot of (useless) retries. Perhaps its simpler not to update the metar on IO error and continue silently. Which version of FlightGear are you using? This has been fixed a long time ago. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d _ FREE pop-up blocking with the new MSN Toolbar - get it now! http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
Harald JOHNSEN wrote: Another problem not related to pure performance is that the first retrieval of metar data can block FG for a long time (perhaps one minute) when the metar server is not accessible (or when there is any network problem). The code does a lot of (useless) retries. Perhaps its simpler not to update the metar on IO error and continue silently. Which version of FlightGear are you using? This has been fixed a long time ago. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
Drew wrote: FlightGear takes nearly a minute to start up from my Windows build, and I'm just wondering if there's an easy way to shorten this if I'm not using all of flightgear's features. Is there one particular task that takes particularly long? ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d Another problem not related to pure performance is that the first retrieval of metar data can block FG for a long time (perhaps one minute) when the metar server is not accessible (or when there is any network problem). The code does a lot of (useless) retries. Perhaps its simpler not to update the metar on IO error and continue silently. Harald. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
Drew wrote: Interesting...I have no use for navaid data. Is there an option to turn these off? And as far as airports go, I only care about the imagery. Any other info, I can do without. Hmmm, that would probably free up a lot of memory too, huh? I'll look into limiting the region of airports it loads. I find it odd that it takes 5 minutes for you...I'm by no means running it on a top-of-the-line gaming machine...a Centrino laptop 1600 MHz with 256 Megs of RAM and a Mobility Radeon 9000 graphics card. Edit apt.dat and runways.dat, just leave KSFO for example. Normaly you should leave a few others used in ai or atc (I don't remember) or disable this functionalities if you don't want an abort of FG. Harald. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
Interesting...I have no use for navaid data. Is there an option to turn these off? And as far as airports go, I only care about the imagery. Any other info, I can do without. Hmmm, that would probably free up a lot of memory too, huh? I'll look into limiting the region of airports it loads. I find it odd that it takes 5 minutes for you...I'm by no means running it on a top-of-the-line gaming machine...a Centrino laptop 1600 MHz with 256 Megs of RAM and a Mobility Radeon 9000 graphics card. On 5/24/05, Vivian Meazza <[EMAIL PROTECTED]> wrote: > Drew wrote > > > FlightGear takes nearly a minute to start up from my Windows build, > > and I'm just wondering if there's an easy way to shorten this if I'm > > not using all of flightgear's features. Is there one particular task > > that takes particularly long? > > > > Only a minute eh? Under Cygwin cvs takes nearly 5 minutes - time for a brew > a coffee - and that's on a pretty powerful machine. The majority of this > time seems to be taken up by the loading of Airport and Navaid data. As I > understand it, the program loads all that are available without regard for > the location of the aircraft. Keeping this number to a minimum should help. > The other variable under your control is the number of scenery objects, but > this doesn't seem to take all that much tile anyway. > > We really need to sort this one. > > Regards, > > Vivian > > > > ___ > Flightgear-devel mailing list > Flightgear-devel@flightgear.org > http://mail.flightgear.org/mailman/listinfo/flightgear-devel > 2f585eeea02e2c79d7b1d8c4963bae2d > ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] FlightGear startup time
Vivian Meazza writes: > > Drew wrote > > > FlightGear takes nearly a minute to start up from my Windows build, > > and I'm just wondering if there's an easy way to shorten this if I'm > > not using all of flightgear's features. Is there one particular task > > that takes particularly long? > > > > Only a minute eh? Under Cygwin cvs takes nearly 5 minutes - time for a brew > a coffee - and that's on a pretty powerful machine. The majority of this > time seems to be taken up by the loading of Airport and Navaid data. As I > understand it, the program loads all that are available without regard for > the location of the aircraft. Keeping this number to a minimum should help. > The other variable under your control is the number of scenery objects, but > this doesn't seem to take all that much tile anyway. > > We really need to sort this one. I adbandoned Cygwin for MingW years ago for just this reason Norman ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
"Vivian Meazza" wrote: > Drew wrote >> FlightGear takes nearly a minute to start up from my Windows build, >> and I'm just wondering if there's an easy way to shorten this if I'm >> not using all of flightgear's features. Is there one particular task >> that takes particularly long? > Only a minute eh? Under Cygwin cvs takes nearly 5 minutes - time for a brew > a coffee - and that's on a pretty powerful machine. At home I run FG on a 400 MHz CPU (on a Unix system), probably not _that_ much compared to your setup. It takes approximately one minute to let FlightGear walk through its initialization - which makes me think that the problem does not lie in FG but in the Cygwin environment instead. On the other hand I would not hold anyone off from optimizing the startup procedure ;-) Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] FlightGear startup time
Drew wrote > FlightGear takes nearly a minute to start up from my Windows build, > and I'm just wondering if there's an easy way to shorten this if I'm > not using all of flightgear's features. Is there one particular task > that takes particularly long? > Only a minute eh? Under Cygwin cvs takes nearly 5 minutes - time for a brew a coffee - and that's on a pretty powerful machine. The majority of this time seems to be taken up by the loading of Airport and Navaid data. As I understand it, the program loads all that are available without regard for the location of the aircraft. Keeping this number to a minimum should help. The other variable under your control is the number of scenery objects, but this doesn't seem to take all that much tile anyway. We really need to sort this one. Regards, Vivian ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
