Q25 of 38 · Performance

What is volume testing and when would you use it?

PerformanceJuniorperformancevolume-testingdata-volumescalabilitydatabase

Short answer

Short answer: Volume testing verifies that the system behaves correctly when it handles large amounts of data — not concurrent users, but data size. Use it when the system processes large files, long-running queries, or tables that grow over time.

Detail

Volume testing is often confused with load testing, but the variable is data volume rather than concurrent users. A system that handles 1,000 simultaneous users fine might fail or degrade when the database reaches 100 million rows, a CSV import file is 500 MB, or a report query spans 3 years of transactions.

Typical volume scenarios:

  • Import a product catalogue with 1 million SKUs and verify completion time and data integrity.
  • Run a report against a database seeded to projected 5-year size.
  • Process a log file at the upper end of the documented file size limit.
  • Verify that search index performance holds as the corpus grows.

Volume testing often requires a dedicated test environment with a large realistic dataset — it cannot be run against a small development database. The planning effort to generate representative data at scale is frequently underestimated.

// WHAT INTERVIEWERS LOOK FOR

Clear distinction: volume = data size, not user concurrency. Practical examples of where it matters. Awareness that it requires a representative large dataset, not just more VUs.