[FYI] ben.woodhouse
#ROBOMERGE-SOURCE: CL 16554462 via CL 16554473 via CL 16554480 via CL 16554514
#ROBOMERGE-BOT: STARSHIP (Release-Engine-Staging -> Release-Engine-Test) (v828-16531559)
#ROBOMERGE[STARSHIP]: UE5-Main
[CL 16554515 by robert millar in ue5-release-engine-test branch]
#ROBOMERGE-SOURCE: CL 16509803 via CL 16509813 via CL 16509817 via CL 16509820
#ROBOMERGE-BOT: STARSHIP (Release-Engine-Staging -> Release-Engine-Test) (v826-16501804)
#ROBOMERGE[STARSHIP]: UE5-Main
[CL 16509821 by robert millar in ue5-release-engine-test branch]
trace.pause/resume - pauses and resumes the tracing of events
trace.send <host> - send a trace over the wire to "host".
#rb jb
[CL 16507790 by Martin Ridgers in ue5-main branch]
StallDetector:
* Replace static and per-callsite counter variables with trace classes
* Compose a trace api appropriate counter name (Stall Detector category)
SummarizeTraceCommandlet:
* Add support for extract and decode of counter messages from utrace files with a new analyzer class
* Report counters with name and count columns in the existing csv
* Support generation of counter events and values through to telemetry csv
#jira UETOOL-3506
#rb francis.hurteau
#preflight 609c5f45e88e9100010b5466
[CL 16314462 by geoff evans in ue5-main branch]
- Added new trace events to track the ReOpenFile API. Updated the PlatformFileTraceAnalysis to process the respective new trace events. This fixes the issue where activities were displayed in Unreal Insights as I/O events with "Unknown" file (UE-114506).
- Updated warning messages and debug code in PlatformFileTraceAnalysis.
- Added handle tracking in Insights for I/O Activity events. File handle and read/write handles are now displayed in tooltip of an I/O Activity event.
- Added "ReOpen" as a separate I/O activity type.
#jira UE-114506
#rb Catalin.Dragoiu, Robert.Millar
[CL 16310259 by ionut matasaru in ue5-main branch]
#ROBOMERGE-OWNER: ben.woodhouse
#ROBOMERGE-AUTHOR: ben.woodhouse
#ROBOMERGE-COMMAND: _robomerge ue5-main
#ROBOMERGE-SOURCE: CL 16110729 via CL 16110730 via CL 16110731 via CL 16110732 via CL 16110733 via CL 16110734
#ROBOMERGE-BOT: STARSHIP (Release-Engine-Staging -> Main) (v789-15992632)
[CL 16117118 by ben woodhouse in ue5-main branch]
- Implement ability to unset metadata values by setting with nullptr
- Sanitize metadata to remove commas from values and keys (the commandline is excluded because it's special)
- Set a starttimestamp metadata value (in seconds since the Unix epoch).
- Add metadata for OS, CPU, Namedevents (at capture start)
- Log metadata changes
[FYI] james.doverspike,andrew.ladenberger
#ROBOMERGE-OWNER: ben.woodhouse
#ROBOMERGE-AUTHOR: ben.woodhouse
#ROBOMERGE-COMMAND: _robomerge ue5-main
#ROBOMERGE-SOURCE: CL 16110194 via CL 16110198 via CL 16110202 via CL 16110209 via CL 16110215 via CL 16110345
#ROBOMERGE-BOT: STARSHIP (Release-Engine-Staging -> Main) (v789-15992632)
[CL 16117042 by ben woodhouse in ue5-main branch]
Removing callstack tracing worker thread. Profiling shows that the performance impact is negligable. Additionally it solves some deadlock issues and makes the code simpler. In order to only trace unique callstack we track emitted ones in a TSherwoodSet. The insertion performance for this collection is very efficient (see https://probablydance.com/2017/02/26/i-wrote-the-fastest-hashtable/) which means offloading it to a worker thread was not giving the expected gains.
#rb martin.ridgers
#rnx
[CL 16089889 by Johan Berg in ue5-main branch]
