One, Two Quesstions regarding Peformance

[blackwinged]

Hi!

I recently wondered if Ogre is performant and when Ogre will break down.

1) Ogre uses a lot of Listeners and User-Defined events. Is this really performanf when developing a game? What is a number of registered Listeners Ogre easily can handle ?

2) A lot of game logic is handled with casting Rays! Walking on Terrain for characters and the player uses it, Mouse Picking uses it, and when u want to determine if a NPC spots the player, one has to cast a ray as well. When you sum it up, there is a lot of ray casting every frame. How much rays in one frame can ogre handl before breaking down?

Thanks!

(Maybe I'll have some other performance issues at a later time)

[Kencho]

About the first question, the number of listeners in use is up to you. It has been discussed many times in these forums about why using one listener per object (for example) is a horrible thing for performance. If your design is good enough, you can speed up things a lot. Ogre just does its work, and does it perfectly

About the second question, well, again, the amount of rays casted is up to you. Terrain height is done each frame, I agree. But target spotting can be done once each 0.5-1 seconds, and mouse picking is done under demand (just in the frame a click is done), so performance shouldn't suffer from that. Again, a problem of design and performance tunning by your side, not Ogre's

Hope that helps

[blackwinged]

hmm but how performant is a Listener System per se compared to other technologies ? And how performant is the implementation in Ogre ?

thanks

[haffax]

There is no performance penalty when using listeners. They are just a way to implement the observer pattern, hence notification about some events.
There is really few that one can do wrong with implementing listeners really. They are stored mostly in std::sets iirc. So insert/remove are both O(log n) instead of O(1)/O(n) for some other containers, but this is absolutly irrelevant since you do this only in setup and cleanup mostly. Calling the observers is a method call for each observer.

I don't know what you want it to be compared against. The other "technology" (looked at too many ads? ) would be using callback functions probably. The performance is more or less equal, but it is not an OO way and rather ugly.

Compared to everything other that has to be done in an application, the listener "overhead" is neglegtable.

[alphageek]

Ogre performance can be excellent or it can be bad, depending on whether you use the most appropriate features.

A more interesting question might be: "I want to do X, what's the best way to go about it?"