I've been profiling the game I'm playing around with to check for any performance bottlenecks, and the ruby-prof accused that the Gosu::Window#show_internals is consuming 45%.
I tried to search what this mean but found nothing :/, can anyone help?
Originally there only used to be
, the C++ function that runs the game's main loop, and which can be safely ignored when looking at a profiler.
However, due to the way exceptions have to be handled and translated across C++ and Ruby, Gosu renames the C++ function to
and defines a new method called
with additional exception handling:https://github.com/jlnr/gosu/blob/master/lib/gosu/swig_patches.rb
tl;dr it's just
in disguise. :)
Hmm I understand,
After all my problem was the map drawing (a lot of tiles), but .record solved my problem right away.
But good to know about the #show_internals, now I know it's ok to ignore it on the profiler results haha.
Powered by mwForum 2.29.7 © 1999-2015 Markus Wichitill