21-04-2005, 07:54 PM
I made some stress test with the database, after one flight I saved the same flight in a loop 7500 times.
-The detailed flight database increased until 3mo
-The index flight database increased to 622ko (the one that is loaded usually if you don't want to display a complete flight report)
-Attempting to display the complete flight report of flight #7500 displayed in 0.01 secondes
-All others flight complete report displayed in 0.01 seconds. (select in index the flight you want, click on it to have complete report)
-Map displayed the 7500 flight in less than 0.5 seconds
-Memory usage was still low (no memory leak)
-Aircraft and pilots stats recorded without flaw.
-No crash, no problems.
About code I have since start a memory leak survey (debug mode) FsP is memory leak proof.
No crash reported due to FsP yet by tester and still about no framerate impact when you are in a "FsP flight"
Fsp source contain now 40'911 lines of C++ and assembly. (net, without comments lines)
Strict coding is paying back.
Dan
Post Edited ( 04-21-05 21:07 )
-The detailed flight database increased until 3mo
-The index flight database increased to 622ko (the one that is loaded usually if you don't want to display a complete flight report)
-Attempting to display the complete flight report of flight #7500 displayed in 0.01 secondes
-All others flight complete report displayed in 0.01 seconds. (select in index the flight you want, click on it to have complete report)
-Map displayed the 7500 flight in less than 0.5 seconds
-Memory usage was still low (no memory leak)
-Aircraft and pilots stats recorded without flaw.
-No crash, no problems.
About code I have since start a memory leak survey (debug mode) FsP is memory leak proof.
No crash reported due to FsP yet by tester and still about no framerate impact when you are in a "FsP flight"
Fsp source contain now 40'911 lines of C++ and assembly. (net, without comments lines)
Strict coding is paying back.
Dan
Post Edited ( 04-21-05 21:07 )