rusefi
/
rusefi_documentation
mirror of https://github.com/rusefi/rusefi_documentation.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Updated Developer Performance Tracing (markdown)

This commit is contained in:
rusefillc 2024-02-22 21:00:13 -05:00
parent 953e9263c5
commit 361fea3272
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
Developer-Performance-Tracing.md
View File

@ -19,15 +19,16 @@ Uses:
## Capturing a Trace ## Capturing a Trace
Use "Grab PTrace" button in rusEFI console, this would request a 500ms performance trace from ECU and write it into a .json file. Use "Grab PTrace" button in rusEFI console, this would request a 500ms performance trace from ECU and write it into a .json file.
Use the W/A/S/D keys to move left, right, or zoom in and out.
Open Google Chrome browser, open chrome://tracing/, load generated .json file. Open Google Chrome browser, open chrome://tracing/, load generated .json file.
## Interpreting a Trace ## Interpreting a Trace
Here is an example of a trace that spans 500 microseconds - 1/2000 of a second: Here is an example of a trace:
< image 1 here > ![image](https://github.com/rusefi/rusefi/assets/48498823/786beb42-e733-4cb8-9609-ab3d692fb9ec)
Across the top of the frame are the timestamp in microseconds - this view shows 4700-5200us. Across the top of the frame are the timestamp in microseconds - this view shows 4700-5200us.