[JAVA][Beginning Java 8 Games Development]

Chapter 7 ■ The Foundation of Game Play Loop: The JavaFX Pulse System and the Game Processing Architecture
Figure 7-21. Run the Live Results Profiler
As you can see, the Invocations column indicates how many pulses have accessed the .handle() method in
the GamePlayLoop. It has only taken 40.1 milliseconds to process 3,532 pulses, so each pulse equates to 0.0114
milliseconds, or 114 nanoseconds, using the new Java 8 timing resolution. Thus, your current code for testing the
pulse, or at least the JavaFX pulse engine, is running efficiently.
Of course, you will need to remove this pulse engine testing code from the .handle() method before moving on to
the next chapter, when you will start processing game assets and logic inside this method.
Next, let’s scroll down one last time in the Profiler tab, displayed at the top left of Figure 7-21, and click the
Threads icon, which is shown at the top left of Figure 7-22, to open the Threads tab. As you can see, the pulse engine
is running, and pulse events can be seen processing in Thread-6 as well as the JavaFX Application Thread.
162
www.it-ebooks.info