Hi Durk,

> Firstly, yesterday I managed to speed-up the replay system, by using
> dynamic allocation instead of pushing copies of rather large objects into
> the STL lists. Using the timestamping code I mentioned yesterday, and
> committed to CVS earler today, I found that memory allocation was very slow
> on my machine. By preallocating a significant number of replay objects, and
> recycling used ones instead of reallocating them I managed to get minimize
> the amount of replay timing errors considerably.

Concerning the replay subsystem, I also found what appears to be a c'n'p error 
in FGReplay::init(), which results in the long term queue not being cleared. 
Probably not significant in this case, though...


Index: replay.cxx
===================================================================
RCS file: /var/cvs/FlightGear-0.9/source/src/Aircraft/replay.cxx,v
retrieving revision 1.5
diff -u -r1.5 replay.cxx
--- replay.cxx  21 Mar 2006 18:52:19 -0000      1.5
+++ replay.cxx  30 Sep 2007 16:30:50 -0000
@@ -76,8 +76,8 @@
     while ( !medium_term.empty() ) {
         medium_term.pop_front();
     }
-    while ( !medium_term.empty() ) {
-        medium_term.pop_front();
+    while ( !long_term.empty() ) {
+        long_term.pop_front();
     }
 }

bye,
        Manuel

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Reply via email to