Andy Ross writes:
These are clearly related to texture loading. How long did you run
your profiler for? If it was just for a few seconds, then these might
be showing the time spent in initialization and not in the routine
frame-to-frame running of the program. Certainly, parsing and
On Wed, 27 Feb 2002 11:28:01 -0500
David Megginson [EMAIL PROTECTED] wrote:
The good news is that the JSBSim matrix support isn't
showing up on the radar screen any more.
Thanks to the work by Norman and Tony (IIRC). I think we
can still make some improvements in JSBSim and I want to
try
Tony Peden writes:
It seems very strange to me, however, that FGInterface::operator=
would show up at all. According to that output, it was called
almost 200,000 times. What's up with that?
Do we keep two copies and swap between them?
All the best,
David
--
David Megginson
[EMAIL
On Wed, 2002-02-27 at 10:59, Tony Peden wrote:
On Wed, 2002-02-27 at 10:22, David Megginson wrote:
Tony Peden writes:
It seems very strange to me, however, that FGInterface::operator=
would show up at all. According to that output, it was called
almost 200,000 times. What's up
On Wed, 2002-02-27 at 09:00, Vallevand, Mark K wrote:
I probably doesn't get called that many times. Most profiling
software picks up some cruft. There is probably some bit of code
located just after FGInterface::operator= that *is* called a lot,
but doesn't have any debug information
David wrote:
For example, the
program spent 2.95% of its time in ssgVtxTable::getNumVertices,
This simply calls getNum of the list, which simply returns a member
variable:
int getNum (void) { return total ; }
See ssg.h.
David
Bye bye,
Wolfram.
PROTECTED]]
Sent: Wednesday, February 27, 2002 1:26 PM
To: FGFS Devel
Subject: RE: [Flightgear-devel] Profiling run
On Wed, 2002-02-27 at 09:00, Vallevand, Mark K wrote:
I probably doesn't get called that many times. Most profiling
software picks up some cruft. There is probably some bit
is getting counts that are really
for funcb.
Regards.
Mark K Vallevand
Fat, dumb and happy. 2 out of 3 ain't bad.
-Original Message-
From: Tony Peden [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 27, 2002 1:26 PM
To: FGFS Devel
Subject: RE: [Flightgear-devel
calc_magvar() is interesting ... that might be something we wouldn't
have to do every frame ...
For what this may be worth, where I work (Rockwell Collins), we do mag var
computations about once every two minutes. Even given some of the
aircraft for which we design (KC-135, B-1B, 747),
David Megginson wrote:
I did another run, with a flight of over one hour on autopilot.
Cumulatively, ssgEntity::cull_test and ssgBranch::cull use nearly 20%
of CPU time -- that's OK, as long as the framerate improvements
justify the work.
Yes - that's probably not too bad...but with it
Wow, good stuff. Skimming through to apply my own intuition:
6.99% ssgEntity::cull_test
5.28% ssgBranch::cull
4.85% ssgVtxTable::draw_geometry
3.42% FGHitList::IntersectLeaf
3.28% FGHitList::IntersectBranch
2.85% ssgVtxTable::getNumVertices
2.71% sgFrustum::contains
1.85% sgdPointInTriangle
11 matches
Mail list logo
