From 2474e480200a8dfa260a069730c19c4bb2cbdf8e Mon Sep 17 00:00:00 2001 From: Valentin Popov Date: Sat, 18 Jul 2026 13:24:00 +0400 Subject: [PATCH] feat(runtime): trace visual graph sizes --- apps/fparkan-game/src/main.rs | 8 +++++-- crates/fparkan-assets/src/lib.rs | 26 +++++++++++++++++++++ crates/fparkan-runtime/src/lib.rs | 38 ++++++++++++++++++++++++------- docs/tomes/05-render.md | 7 ++++++ 4 files changed, 69 insertions(+), 10 deletions(-) diff --git a/apps/fparkan-game/src/main.rs b/apps/fparkan-game/src/main.rs index 465a98a..414ee71 100644 --- a/apps/fparkan-game/src/main.rs +++ b/apps/fparkan-game/src/main.rs @@ -1089,14 +1089,18 @@ mod tests { write_load_progress( &path, std::time::Duration::from_millis(34), - MissionLoadPhase::GraphVisualMaterialRequests(64), + MissionLoadPhase::GraphVisualMaterialRequests { + request_count: 64, + graph_node_count: 128, + graph_edge_count: 192, + }, )?; let progress = std::fs::read_to_string(&path).map_err(|err| err.to_string())?; std::fs::remove_file(&path).map_err(|err| err.to_string())?; assert_eq!( progress, - "Starting\telapsed_ms=0\nGraphVisualMaterials\telapsed_ms=12\nGraphVisualMaterialRequests(64)\telapsed_ms=34\n" + "Starting\telapsed_ms=0\nGraphVisualMaterials\telapsed_ms=12\nGraphVisualMaterialRequests { request_count: 64, graph_node_count: 128, graph_edge_count: 192 }\telapsed_ms=34\n" ); Ok(()) } diff --git a/crates/fparkan-assets/src/lib.rs b/crates/fparkan-assets/src/lib.rs index 11e324f..6e3364d 100644 --- a/crates/fparkan-assets/src/lib.rs +++ b/crates/fparkan-assets/src/lib.rs @@ -490,6 +490,10 @@ pub struct VisualDependencyProgress { pub phase: VisualDependencyPhase, /// Number of requests reached in this class during the current expansion. pub request_count: usize, + /// Resource graph nodes materialized before this request is resolved. + pub graph_node_count: usize, + /// Resource graph edges materialized before this request is resolved. + pub graph_edge_count: usize, } /// Errors raised while preparing CPU-side assets. @@ -1239,6 +1243,8 @@ pub fn extend_graph_report_with_visual_dependencies_with_progress { @@ -1281,6 +1287,8 @@ pub fn extend_graph_report_with_visual_dependencies_with_progress 1 { let request_phase = match progress.phase { VisualDependencyPhase::Wear => None, - VisualDependencyPhase::Material => Some( - MissionLoadPhase::GraphVisualMaterialRequests(progress.request_count), - ), - VisualDependencyPhase::Texture => Some( - MissionLoadPhase::GraphVisualTextureRequests(progress.request_count), - ), + VisualDependencyPhase::Material => { + Some(MissionLoadPhase::GraphVisualMaterialRequests { + request_count: progress.request_count, + graph_node_count: progress.graph_node_count, + graph_edge_count: progress.graph_edge_count, + }) + } + VisualDependencyPhase::Texture => { + Some(MissionLoadPhase::GraphVisualTextureRequests { + request_count: progress.request_count, + graph_node_count: progress.graph_node_count, + graph_edge_count: progress.graph_edge_count, + }) + } }; if let Some(request_phase) = request_phase { record_load_phase(&mut trace, &mut on_phase, request_phase); diff --git a/docs/tomes/05-render.md b/docs/tomes/05-render.md index b647f19..d390a9a 100644 --- a/docs/tomes/05-render.md +++ b/docs/tomes/05-render.md @@ -1126,6 +1126,13 @@ termination. It does not preserve the simultaneous TEXM count, so it neither identifies a slow individual material nor attributes time to MAT0 parsing; the next profiler revision needs one cumulative snapshot of all classes. +Visual MAT0/TEXM request markers now also carry the graph node and edge counts +materialized immediately before that request resolves. A rebuilt bounded Part 2 +probe recorded MAT0 request 3 at 52 nodes / 51 edges and request 4 at 55 nodes +/ 54 edges. These are observational snapshots for graph-growth profiling only: +they do not change traversal order, node or edge identities, provenance, +validation, cache semantics, or rendering. + `fparkan-game --load-progress` now initializes its file with `Starting` and appends each later mission-load event instead of replacing the prior line. A bounded probe can therefore retain both MAT0 and TEXM request milestones even