Re: [simspark-devel] Re: [Sserver-three-d]Agent Say- and Heareffector

[Markus R. <rol...@un...>]

Hi,

Hesham wrote:
> I'm testing google cpu profiler (
[...]

I just read about google profiler. It looks nice, especially the 
graphical output of the call graph.

> Can I know your opinion about code optimization? do you use any tools
> to analysis the performance of the server?

In general profiling can be a valuable tool if used with caution. But I 
think that readable and maintainable code that is well structured is 
more important than squeezing out the last bit of performance. This is 
especially true if more than one developer is working on a piece of code 
  in an open source project.

The brainstormers 3d team (Germany, Karlsruhe) used a profiler on the 
server and found that most time was spent resolving path names (e.g. 
/sys/server/input) to pointers. Therefore we implemented a node cache to 
speed up the server. So in this case you don't profile a specific 
section of your code (like your offside rule) but try to find out where 
the global bottleneck is.

It would be interesting to know where the soccer simulation spends most 
of its time, i.e. the soccer plugin. Is it possible to limit profiling 
to this plugin?

Another thing: It would be nice if you could document your profiling, 
say/hear  and offside rule work. I.e. how to setup and use the google 
profiler along with a summary of your results. And for the plugins a 
kind of todo/done list.

For the simspark/soccer3d project Oliver already setup a wiki at [1] 
(the editing password is 'spark'). It's intended as a shared todo list 
and documentation wiki if you like.

regards,
Markus

[1] http://simspark.sourceforge.net/pmwiki/