A new tool enables importing JDK Flight Recorder (JFR) profiling files into DuckDB databases for SQL-based analysis. The post covers the data modeling decisions: how JFR events map to tables, how structs are either inlined (numeric-only or single-property) or given separate tables with _id references, and how stack traces are

15m read timeFrom mostlynerdless.de
Post cover image
Table of contents
TL;DRPreviouslyAlternativesWhy DuckDBGoals and Non-GoalsModelling JFR Events as TablesInlined StructsReferenced StructsStack TracesFront-EndNameToolConclusionAuthorRelated Posts:

Sort: