Profiling

[hovsep]

Add StartedAt, FinishedAt, Duration on cycle and activation result level
Profile each component and pipe (how many times activated, how many signals flown, activation duration)

[hovsep]

this can be implemented as plug in

[hovsep]

Status check against main — the timing half is done, the counting half is not.

Done: plugin.Profiler (plugin/profiler.go) measures whole runs, single cycles, and each component's activations, as count / total / min / max / avg, with TopN and a Report() string. It reaches every component through the OnComponentAdded hook, so nothing in a mesh has to be written differently to be measured:

p := plugin.NewProfiler()
fm := fmesh.New("mesh", fmesh.WithPlugins(p))
_, _ = fm.Run(ctx)
fmt.Println(p.Report())

The per-component numbers are the ones a Go CPU profile cannot give you — a profile of a mesh is dominated by the scheduler, because every component's work is the same handful of runtime calls.

Still open, both from the description:

1. StartedAt / FinishedAt / Duration on cycle.Cycle and ActivationResult. Neither type carries any time field today; the profiler keeps its own timings in a side map. Putting them on the types would make them visible from RuntimeInfo without a plugin.
2. Pipe-level stats — how many signals flowed through each pipe. The profiler counts activations only, and nothing anywhere counts signals per pipe.