[sldev] Is anyone using gcc -pg (profiling) to see where the CPU is being consumed?

[Max Okumoto]

Callum Lerwick wrote:
> On Wed, 2007-06-13 at 17:47 -0700, Max Okumoto wrote:
>   
>> I have a patch to enable builds of the linux client with profiling, and 
>> I'm trying to see what
>> routines are eating the CPU.  Is anyone else doing this.  I would like 
>> to compare notes.
>>     
>
> Profiling using oprofile on my rather low end laptop, (Celeron 1.3,
> Intel 830M video) OpenJPEG and the OpenGL drivers (in particular,
> lighting) dominate. So I've put quite a bit of time and effort into
> optimizing OpenJPEG. OpenJPEG 1.2 merged a few of them but I keep coming
> up with new ones. :) (And regression testing is painful and
> slowgoing...)
>   
Wow, isn't that painful?

Right now, I only have the slviewer source tree itself compiled with 
profiling.  The top 5 routines are

Each sample counts as 0.01 seconds.
  %   cumulative   self              self     total
 time   seconds   seconds    calls   s/call   s/call  name
  4.00      5.23     5.23   753687     0.00     0.00  
LLVOSky::calcSkyColorInDir(LLColor3&, LLColor3&, LLVector3 const&) const
  3.34      9.59     4.36  4198499     0.00     0.00  
LLFace::getGeometryVolume(LLVolume const&, int, LLStrider<LLVector3>&, 
LLStrider<LLVector3>&, LLStrider<LLVector2>&, LLStrider<LLVector2>&, 
LLStrider<LLColor4U>&, LLStrider<unsigned int>&, LLMatrix4 const&, 
LLMatrix3 const&, unsigned int&)
  3.30     13.90     4.31  1703493     0.00     0.00  
LLVolumeFace::createSide()
  3.07     17.91     4.01  1025310     0.00     0.00  
LLViewerJointMesh::updateGeometry()
  2.95     21.76     3.85 31594072     0.00     0.00  
LLPipeline::calcPixelArea(LLVector3, LLVector3, LLCamera&)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.secondlife.com/pipermail/sldev/attachments/20070614/abcbfe64/attachment-0001.htm