Allocation Profile — Folded Stacks Weighted in Bytes (txt)
An allocation profile in the same folded syntax as the CPU profiles, but weighted in bytes rather than samples. The format carries no unit, so a viewer that assumes samples renders 65 MB of allocation as 68 million samples — which is what this fixture is for.
main;checkout.Handle;encoding/json.Unmarshal;makeslice 68157440
main;checkout.Handle;pricing.total;makemap_small 12582912
main;checkout.Handle;fmt.Sprintf;runtime.concatstrings 41943040
main;checkout.Handle;inventory.Reserve;grpc.(*ClientConn).Invoke;makeslice 25165824
main;metrics.flushLoop;prometheus.(*Registry).Gather;makeslice 8388608
main;http.(*conn).serve;bufio.NewReaderSize;makeslice 16777216
Specifications
- Stacks
- 6
- Unit
- bytes
- Total Bytes
- 173015040
- Largest Stack Bytes
- 68157440
- Max Depth
- 4
- Note
- same syntax as a CPU profile, different weight unit
Testing contract
Expected to pass- Scenario
- Render the profile with an explicit byte unit and read the largest allocator.
- Expected result
- The JSON Unmarshal path reports 65 MiB rather than 68,157,440 samples, and the total matches the sum of the six stacks.
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
“Allocation Profile — Folded Stacks Weighted in Bytes (txt)” is a deterministic Novus Examples fixture for Observability, Performance testing, Conversion testing. 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: TXT · 404 bytes. 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
- jsonChrome DevTools CPU Profile — Node Tree with Sample Deltas (json)The .cpuprofile shape V8 emits: a node tree with call frames, a samples array of node IDs and a parallel timeDeltas array, plus the synthesized (idle), (program) and (garbage collector) nodes. Counting those synthetic frames as application time is the classic misreading.
- txtCPU Profile — Folded Stacks After a Regression (txt)The same workload after a change: JSON decoding costs four times as much and gains a new reflect frame, while cache lookups get cheaper. Paired with the baseline so a differential flamegraph can be scored against a known regression and a known improvement.
- txtCPU 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.
- 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.
Generated by generation/observability.py. Free for any use, no attribution required — license.