Documentation
¶
Overview ¶
Command pgnotch-load puts an unbounded append load on pgnotch logs.
It takes everything from its flags, writes at the rate they name from the payload-size distribution they name, and keeps going until it is interrupted. The distribution is the point: a class above pgnotch.MaxEntryChunk is an entry the library has to cut into several rows, which is a different write from a 900-byte one and is not otherwise exercised by a fixed size.
pgnotch-load -dsn postgres://…/db -rps 500 -logs 8 -sizes 1k:9,32k:1
The logs are this tool's own: it creates them, fences them at an epoch of the run's own, appends to them, and trims behind itself so that a run of any length costs a bounded amount of disk. Nothing here reads the logs back for their content — the suites do that; this asks what the write path costs.