- Add support for >,<,>=,<= operators for metadata queries (for numerical fields)
- Use doubles for SummaryTable/SummaryTableColumn values, so we can accurately show display values (does not affect summary cache - this was already at double precision)
#ROBOMERGE-OWNER: ben.woodhouse
#ROBOMERGE-AUTHOR: ben.woodhouse
#ROBOMERGE-COMMAND: _robomerge ue5-main
#ROBOMERGE-SOURCE: CL 16110876 via CL 16110877 via CL 16110881 via CL 16110882
#ROBOMERGE-BOT: STARSHIP (Release-Engine-Staging -> Main) (v789-15992632)
[CL 16117137 by ben woodhouse in ue5-main branch]
- Add -requireMetadata option to ignore CSVs without metadata
- Clean up help text so the lines arent too long for standard console output
#ROBOMERGE-OWNER: ben.woodhouse
#ROBOMERGE-AUTHOR: ben.woodhouse
#ROBOMERGE-COMMAND: _robomerge ue5-main
#ROBOMERGE-SOURCE: CL 16105233 via CL 16105248 via CL 16105254 via CL 16105255
#ROBOMERGE-BOT: STARSHIP (Release-Engine-Staging -> Main) (v789-15992632)
[CL 16116861 by ben woodhouse in ue5-main branch]
- add -summaryTableCacheUseOnlyCsvID param to ignore the ReportType hash and just use the CSV ID for summaryTableCache ID entries. This is a good idea if you want these files to persist and you don't want them to be regenerated when report types change
- Add ReportType and ReportTypeID to the summaryTable ToolMetaData entries
- Use the reportType name as part of the report hash (this will invalidate existing cache files!)
#ROBOMERGE-OWNER: ben.woodhouse
#ROBOMERGE-AUTHOR: ben.woodhouse
#ROBOMERGE-COMMAND: _robomerge ue5-main
#ROBOMERGE-SOURCE: CL 16024419 via CL 16024452 via CL 16024531 via CL 16045954
#ROBOMERGE-BOT: STARSHIP (Release-Engine-Staging -> Main) (v789-15992632)
[CL 16116846 by ben woodhouse in ue5-main branch]
- Refactor code to avoid use of the term Metadata to refer to summary table row data. The term metadata was easily confused with CSV metadata, and in most cases, it wasn't actually metadata.
- This refactor resulted in some minor breaking changes in XML format and command line params. The affected reports and scripts have been fixed up accordingly
The following were renamed:
SummaryMetadata -> SummaryTableRowData
SummaryMetadataValue->SummaryTableElement
SummaryMetadataTable->SummaryTable
metadataKey -> summaryStatName (also affects XML)
metadataPrefix -> summaryStatNamePrefix (also affects XML)
metadataCache -> summaryTableCache
Commandline params, e.g: -metadataCache -> -summaryMetadataCache
#ROBOMERGE-OWNER: ben.woodhouse
#ROBOMERGE-AUTHOR: ben.woodhouse
#ROBOMERGE-COMMAND: _robomerge ue5-main
#ROBOMERGE-SOURCE: CL 16023141 via CL 16023153 via CL 16023173 via CL 16045518
#ROBOMERGE-BOT: STARSHIP (Release-Engine-Staging -> Main) (v789-15992632)
[CL 16116817 by ben woodhouse in ue5-main branch]
-5x faster metadata cache only reads:
- Only read the initial CSV metadata entries before metadata filtering (since these always appear first)
- Skip report type determiniation in metadataonly mode (this is slow and unnecessary)
-crash fix (don't crash if old version metadata is encountered, just skip and log)
Querying a single device profile across 31k CSVs of mixed device profiles takes 2.1s instead of 10.2s previously
#ROBOMERGE-OWNER: ben.woodhouse
#ROBOMERGE-AUTHOR: ben.woodhouse
#ROBOMERGE-COMMAND: _robomerge ue5-main
#ROBOMERGE-SOURCE: CL 16015980 via CL 16015986 via CL 16015993 via CL 16043535
#ROBOMERGE-BOT: STARSHIP (Release-Engine-Staging -> Main) (v789-15992632)
[CL 16116807 by ben woodhouse in ue5-main branch]
Open metadata and .bin files readonly
#ROBOMERGE-OWNER: ben.woodhouse
#ROBOMERGE-AUTHOR: ben.woodhouse
#ROBOMERGE-COMMAND: _robomerge ue5-main
#ROBOMERGE-SOURCE: CL 16013849 via CL 16013851 via CL 16013859 via CL 16043212
#ROBOMERGE-BOT: STARSHIP (Release-Engine-Staging -> Main) (v789-15992632)
[CL 16116794 by ben woodhouse in ue5-main branch]
- Add -metadataCacheIn mode for running without CSVs
- Use a BlockingCollection to eliminate precache threading bottleneck and simplify precache thread producer/consumer code
- Threading still hits a performance bottleneck at around 6 threads when running metadata queries currently, and gets slower after that as more threads are added.
- Need further work to optimize GetReportTypeXML (too much unnecessary linq) and SummaryMetadata::TryReadFromCache
#ROBOMERGE-OWNER: ben.woodhouse
#ROBOMERGE-AUTHOR: ben.woodhouse
#ROBOMERGE-COMMAND: _robomerge ue5-main
#ROBOMERGE-SOURCE: CL 15974021 via CL 15974024 via CL 15974028 via CL 16027282
#ROBOMERGE-BOT: STARSHIP (Release-Engine-Staging -> Main) (v789-15992632)
[CL 16112788 by ben woodhouse in ue5-main branch]
- support multiple local player views.
#rb Mickael G.
#ROBOMERGE-SOURCE: CL 11884348 via CL 11884427
#ROBOMERGE-BOT: (v656-11643781)
[CL 11889385 by serge bernier in Main branch]
-metadatafilter "key0=value0,key1=value1,..."
[FYI] serge.bernier,mickael.gilabert
#ROBOMERGE-SOURCE: CL 10761485 via CL 10761498
#ROBOMERGE-BOT: (v610-10636431)
[CL 10761500 by ben woodhouse in Main branch]
- Reduce event spam by grouping duplicate events if they appear within a certain number of pixels of each other. Display the count
- Also reduce the frequency of event lines and reduce the alpha when spamming occurs
#ROBOMERGE-SOURCE: CL 10607478 via CL 10607481
#ROBOMERGE-BOT: (v607-10590470)
[CL 10607482 by ben woodhouse in Main branch]
- Fixes an out-by-one bug with -avg. The stats were being divided by csvCount-1 instead of csvCount
#ROBOMERGE-SOURCE: CL 10505654 via CL 10505655
#ROBOMERGE-BOT: (v606-10482310)
[CL 10505656 by ben woodhouse in Main branch]
- Batched graph generation is enabled by default (disable with -nobatchedgraphs)
- Report generation is 33% faster and no longer consumes the entire CPU
[FYI] will.fissler
#ROBOMERGE-SOURCE: CL 10468949 via CL 10471051
#ROBOMERGE-BOT: (v595-10452236)
[CL 10471304 by ben woodhouse in Main branch]
- Batched + multithreaded support via response files
PerfReportTool 4.00
- Support batched graph generation. Increases perf by 30% over old multi process method. Significantly lower CPU and disk usage too. Enable with -batchedgraphs
- Fixed determinism issues with report generation. Test cases are now identical between runs
#ROBOMERGE-SOURCE: CL 10318336 via CL 10318337
#ROBOMERGE-BOT: (v593-10286020)
[CL 10318338 by ben woodhouse in Main branch]
