Sample files for performance and load testing

Large, predictable inputs for measuring throughput, memory use and processing time.

Performance problems in file handling are rarely visible with small inputs. Memory use that is negligible at 10 KB becomes an outage at 10 MB if the code reads whole files into memory, and a parser that seems instant can turn out to be quadratic.

Testing with a ladder of sizes, each ten times the last, shows how time and memory grow. If a tenfold increase in input costs much more than a tenfold increase in time, there is something to fix.

Recommended files

FileSizeWhy this oneDownload
10 MB CSV samplesample-csv-10mb.csv10 MB10,485,760 bytesImport throughputDownload CSV
10 MB JSON samplesample-json-10mb.json10 MB10,485,760 bytesParser memory useDownload JSON
10 MB XLSX samplesample-xlsx-10mb.xlsx10 MB10,485,760 bytesSpreadsheet import with hundreds of thousands of rowsDownload XLSX
10 MB JPG samplesample-jpg-10mb.jpg10 MB10,485,760 bytesImage decode memoryDownload JPG
10 MB BIN samplesample-bin-10mb.bin10 MB10,485,760 bytesNetwork throughputDownload BIN

Checklist

  1. Measure a size ladder

    Run the same operation on 100 KB, 1 MB and 10 MB files and compare how time and peak memory scale.

  2. Watch memory, not only time

    Peak memory several times the file size indicates buffering or a DOM-style parser.

  3. Test concurrency

    Ten simultaneous 10 MB uploads behave very differently from one. Check queueing, back-pressure and temporary disk use.

  4. Use incompressible data for network tests

    Text files flatter your numbers when compression is enabled.

Guides

Related use cases

Frequently asked questions

How large an image does the 10 MB JPG decode to?
Its pixel dimensions are listed on the download page. Multiply width by height by four to estimate the bytes of memory needed to hold it decoded.