On 4 Oct 2012, at 07:27, Renk Thorsten wrote: > By printing a message like 'Building database during first startup' on the > screen?
That's already done. > By including the binary nav data with the release? This is possible but there's something weird going on with some people's rebuilds. Touching the files will cause a rebuild, so rebuilds need to take a 'reasonable' amount of time. Shipping the binary data improves first-launch perceptions, but many applications do additional work on their first launch after an install, so it's not my top concern. As I said in the bug, my concern is why the rebuild times are so bad for some people - it's purely a CPU / disk-bound operation, and for me and all people I've asked, it's around the ~60sec for debug, ~30sec for release times for a complete rebuild. (That time will be dramatically reduced if we get the taxiway data out of apt.dat in the future, since taxiways account for >80% of the lines in the file). Regards, James ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
