I have been profiling Wesnoth with Shark and Instruments on OS 10.5, the results which still need a bit of mining and statistical analysis show that Wesnoth spends a majority of its time ( ~ 85% ) in the graphics and audio routines, a large amount of time blocking in the main loop ( between ~3% and ~7% ), and lastly about ( ~ 3% ) combined allocating std::string, copying std::strings and comparing std::strings in maps. Most other operations weigh in under 0.1%. These numbers, as I said need refining, and as I only have had time for a sample size of three runs ( they take quite some time ) they may change.
Before I do anymore runs, do these numbers line up roughly with expectations and previous analysis? Is there a better testing scenario? .- .-- _______________________________________________ Wesnoth-dev mailing list [email protected] https://mail.gna.org/listinfo/wesnoth-dev
