CPU Profile — Folded Stacks, Baseline (txt)
A CPU profile in the folded-stack format every flamegraph tool reads: one line per unique stack, frames separated by semicolons, then a space and a sample count. Twelve stacks up to seven frames deep, with the runtime's GC and scheduler work included as real profiles have.
main;runtime.main;http.ListenAndServe;http.(*conn).serve;checkout.Handle;checkout.price;pricing.applyDiscount 4120
main;runtime.main;http.ListenAndServe;http.(*conn).serve;checkout.Handle;checkout.price;pricing.lookupRate;sql.(*DB).QueryContext 2880
main;runtime.main;http.ListenAndServe;http.(*conn).serve;checkout.Handle;checkout.price;pricing.lookupRate;cache.Get 1440
main;runtime.main;http.ListenAndServe;http.(*conn).serve;checkout.Handle;encoding/json.Marshal;encoding/json.(*encodeState).marshal 3310
main;runtime.main;http.ListenAndServe;http.(*conn).serve;checkout.Handle;encoding/json.Unmarshal;encoding/json.(*decodeState).object 2190
main;runtime.main;http.ListenAndServe;http.(*conn).serve;checkout.Handle;inventory.Reserve;grpc.(*ClientConn).Invoke 1760
main;runtime.main;http.ListenAndServe;http.(*conn).serve;auth.Verify;crypto/ecdsa.Verify 980
main;runtime.main;http.ListenAndServe;http.(*conn).serve;middleware.Log;fmt.Sprintf 610
main;runtime.main;metrics.flushLoop;prometheus.(*Registry).Gather 540
main;runtime.main;runtime.gcBgMarkWorker;runtime.scanobject 1880
main;runtime.main;runtime.mcall;runtime.schedule;runtime.findRunnable 720
main;runtime.main;runtime.sysmon 130
Specifications
- Stacks
- 12
- Total Samples
- 20560
- Format
- collapsed/folded (semicolon-separated frames, space, count)
- Max Depth
- 7
- Unit
- samples
- Hottest Leaf
- pricing.applyDiscount
Testing contract
Expected to pass- Scenario
- Render the file as a flamegraph and read off the widest leaf.
- Expected result
- Twelve stacks totalling 20560 samples render into one flamegraph rooted at main, with pricing.applyDiscount the widest leaf at 20.0 percent of the profile.
What is a .txt file?
TXT is a plain-text file containing unformatted character data with no styling or structure beyond line breaks. Its interpretation depends on character encoding, most commonly UTF-8, and on line-ending convention. It is the most universal and portable text container.
How to use this file
Use an example TXT to test encoding detection, line-ending (LF versus CRLF) handling, and any tool that reads or streams raw text input.
How to use this file for testing
“CPU Profile — Folded Stacks, Baseline (txt)” is a deterministic Novus Examples fixture for Observability, Performance testing, Log parsing. Structured and plain-text telemetry with known timestamps, levels, request identifiers, and error states for testing log ingestion, correlation, dashboards, and alert pipelines.
Documented properties for this file: collapsed/folded (semicolon-separated frames, space, count). Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.
Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such — expect parsers to fail loudly rather than silently accept them.
Telemetry fixtures use fixed trace IDs, span IDs, and timestamps so ingestion is reproducible run to run. Point your collector, parser, or query layer at the file and assert the documented span tree, metric families, or severity mix; service and host names are invented.
Related files
- txtLinux perf script — Sample Records with Call Chains (txt)Raw perf script output — a header line per sample followed by tab-indented call-chain frames with addresses, symbols, offsets and DSO paths, samples separated by blank lines. The input side of stackcollapse, including unresolved frames a symbolizer could not name.
- txtpprof — Annotated Source Listing (txt)Line-level profile output: two routines with per-source-line flat and cumulative cost, a dot for lines that cost nothing, and units that switch between seconds and milliseconds within one column. Source lines keep their real tabs, which most column parsers do not survive.
- txtpprof — Top Report Text Output (txt)The text report pprof prints for the same profile as the folded fixtures: a metadata header, then flat and cumulative columns where frames that are never a leaf carry zero flat time and near-total cumulative time. Column-aligned output with a bare 0 rather than 0s, which is where naive column parsing fails.
- txtProfile — 200-Frame Recursive Stack (txt)A recursive-descent parser profiled mid-recursion: stacks up to 204 frames deep where one frame repeats 200 times, on lines over 3,000 characters. Flamegraph renderers with a fixed depth limit truncate this silently, and line-length limits split it into nonsense.
- txtWall-Clock Profile — Per-Thread Folded Stacks (txt)A 30-second wall-clock profile with the thread name as the root frame, so time blocked in reads is visible instead of invisible. Off-CPU time dominates — the shape that tells you a service is waiting, not computing, which a CPU profile alone cannot show.
- jsonlStructured Log — High-Cardinality Label Fields (jsonl)Every record carries five fields that are unique to it — session, customer, device, pod name and container ID. Harmless as log text, ruinous the moment they are promoted to indexed labels, which is the mistake this fixture exists to make measurable.
Generated by generation/observability.py. Free for any use, no attribution required — license.