New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

close gap in scenenode update performance between 1.10 and 2.0 #440

Closed
paroj opened this Issue Jul 11, 2017 · 2 comments

Comments

Projects
None yet
1 participant
@paroj
Collaborator

paroj commented Jul 11, 2017

@paroj

This comment has been minimized.

Collaborator

paroj commented Jul 22, 2017

scenenodebench
https://github.com/paroj/OgreSceneNodeBenchmark

140*140 Nodes = 19600 Nodes

Frametime

Ogre Configuration Static (ms) Animated (ms)
1.10.7 GL 42.64 65.60
1.10.7 GL3+ 89.22 118.54
1.10.7 GL3+ (StateCache) 45.20 64.54
2.0 GL (SSE2, 4 Threads) 27.12 28.98
2.0 GL (C, 4 Threads) 26.97 27.56
2.0 GL (C, 1 Thread) 30.63 32.15
1.10.8 GL (vector storage) 33.10 48.88

Intel(R) Xeon(R) CPU E3-1231 v3 @ 3.40GHz

Memory

Ogre SceneManager MB
1.10.9 Octree 70
1.10.9 default 67
1.11.dev default 63.4
2.0 default 66

@paroj paroj changed the title from measure scenenode update performance between 1.10 and 2.0 to close gap in scenenode update performance between 1.10 and 2.0 Aug 10, 2017

@paroj

This comment has been minimized.

Collaborator

paroj commented Aug 27, 2017

for traversal we are just 10% away from 2.0. Update performance tracked in #506

@paroj paroj closed this Aug 27, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment