search

gfx-rs / gfx_scene

deprecated
Apache License 2.0
15 stars 1 forks source link

[Discussion] Performance numbers #41

Closed ghost closed 9 years ago

ghost commented 9 years ago

I did a little bit of profiling with gfx_scene to get an idea of how well the library was performing. I had a pathologically bad use-case where I was supplying a list of 5000 culled objects to the library (with no culling).

Section Time
Engine 4.0ms
Scene Enqueue 7.7ms
Phase Sort 0.4ms
Phase Draw 136.0ms
Present 1.3ms

In summary, most of our time is spend calling stream.draw

kvark commented 9 years ago

Thanks for the numbers! The fact we are spending time in stream.draw means that gfx_scene itself is not a bottleneck of this case.

ghost commented 9 years ago

@kvark yes that is what I wanted to make sure of. Secondly, if there is a bottlenect it is the Phase enqueue.

I'm getting inconsitent numbers about the cost of stream.draw. I'm investigating it right now. My laptop did not have any problems drawing the scene at 30fps, even with 5000 objects. Which is what I was hoping for.

ghost commented 9 years ago

Since #31 is done, I am closing this issue. Anyone can now gather the same numbers.