6,566
edits
Howto:Use the system monitor: Difference between revisions
Jump to navigation
Jump to search
m
Switch to the {{forum url}} and {{forum link}} templates for all forum links.
m (Switch to the {{forum url}} and {{forum link}} templates for all forum links.) |
|||
| Line 8: | Line 8: | ||
|1= those systems are not "processes", but just "loops" - i.e. whatever the thing is called in the list, you should append "update-loop" to it - and some names are still misleading (events=Nasal). | |1= those systems are not "processes", but just "loops" - i.e. whatever the thing is called in the list, you should append "update-loop" to it - and some names are still misleading (events=Nasal). | ||
|2= {{cite web | |2= {{cite web | ||
| url = | | url = {{forum url|p=264426}} | ||
| title = <nowiki>Re: Su-15</nowiki> | | title = <nowiki>Re: Su-15</nowiki> | ||
| author = <nowiki>Hooray</nowiki> | | author = <nowiki>Hooray</nowiki> | ||
| Line 19: | Line 19: | ||
Finally, it is this "team of people" that will produce a single frame - so whenever "someone" is too slow, it will end up causing stuttering. No matter the reason, scenery/terrain, Nasal etc - at some point, another subsystem will have to wait, which means fewer frames created per second. | Finally, it is this "team of people" that will produce a single frame - so whenever "someone" is too slow, it will end up causing stuttering. No matter the reason, scenery/terrain, Nasal etc - at some point, another subsystem will have to wait, which means fewer frames created per second. | ||
|2= {{cite web | |2= {{cite web | ||
| url = | | url = {{forum url|p=264313}} | ||
| title = <nowiki>Re: Su-15</nowiki> | | title = <nowiki>Re: Su-15</nowiki> | ||
| author = <nowiki>Hooray</nowiki> | | author = <nowiki>Hooray</nowiki> | ||
| Line 34: | Line 34: | ||
|1= the built-in performance monitor, and especially the GUI (it being used in PUI/PLIB)- is adding to the performance overhead you're seeing | |1= the built-in performance monitor, and especially the GUI (it being used in PUI/PLIB)- is adding to the performance overhead you're seeing | ||
|2= {{cite web | |2= {{cite web | ||
| url = | | url = {{forum url|p=243288}} | ||
| title = <nowiki>Re: FlightGear permanently damages the performance of comput</nowiki> | | title = <nowiki>Re: FlightGear permanently damages the performance of comput</nowiki> | ||
| author = <nowiki>Hooray</nowiki> | | author = <nowiki>Hooray</nowiki> | ||
| Line 43: | Line 43: | ||
|1= you will want to use the http/telnet interfaces to watch the performance stats, because the GUI dialog using PUI/Nasal is dead-slow, and even adding to the overhead you are seeing | |1= you will want to use the http/telnet interfaces to watch the performance stats, because the GUI dialog using PUI/Nasal is dead-slow, and even adding to the overhead you are seeing | ||
|2= {{cite web | |2= {{cite web | ||
| url = | | url = {{forum url|p=264313}} | ||
| title = <nowiki>Re: Su-15</nowiki> | | title = <nowiki>Re: Su-15</nowiki> | ||
| author = <nowiki>Hooray</nowiki> | | author = <nowiki>Hooray</nowiki> | ||
| Line 51: | Line 51: | ||
|1= "events" is the subsystem that triggers/runs Nasal timers, and any Nasal code (anywhere), may trigger the GC (garbage collector) - to see if that's the case, you can use the "GC tracker" patch in the sigar code we have. | |1= "events" is the subsystem that triggers/runs Nasal timers, and any Nasal code (anywhere), may trigger the GC (garbage collector) - to see if that's the case, you can use the "GC tracker" patch in the sigar code we have. | ||
|2= {{cite web | |2= {{cite web | ||
| url = | | url = {{forum url|p=258607}} | ||
| title = <nowiki>Re: How to tell if you are CPU or GPU limited (split)</nowiki> | | title = <nowiki>Re: How to tell if you are CPU or GPU limited (split)</nowiki> | ||
| author = <nowiki>Hooray</nowiki> | | author = <nowiki>Hooray</nowiki> | ||
| Line 68: | Line 68: | ||
Note that you can also use the http (browser) or telnet protocols to do this while extending the logging protocol | Note that you can also use the http (browser) or telnet protocols to do this while extending the logging protocol | ||
|2= {{cite web | |2= {{cite web | ||
| url = | | url = {{forum url|p=258579}} | ||
| title = <nowiki>Re: How to tell if you are CPU or GPU limited (split)</nowiki> | | title = <nowiki>Re: How to tell if you are CPU or GPU limited (split)</nowiki> | ||
| author = <nowiki>Hooray</nowiki> | | author = <nowiki>Hooray</nowiki> | ||
| Line 116: | Line 116: | ||
== Discussed Enhancements == | == Discussed Enhancements == | ||
* decouple Nasal events from the "events" subsystem and use a new "events-nasal" instead | * decouple Nasal events from the "events" subsystem and use a new "events-nasal" instead {{forum link|p=164715}} | ||
* show average frame-spacing effect per subsystem as a percentage | * show average frame-spacing effect per subsystem as a percentage | ||
* show memory consumption per subsystem (overload the new operator) | * show memory consumption per subsystem (overload the new operator) | ||