Benchmark compressed input ​

A compressed-input benchmark should answer an application question: whether a chosen input path loads the same rows correctly and improves elapsed time or transferred size for that workload. Report the complete operation, including file preparation when it is part of the user's task.

Establish correctness first ​

Use one fixed source dataset and one destination schema. Load an uncompressed baseline using the documented client file input, then compare the compressed-file variant supported by that input path. Keep compression support tied to the documented path; do not assume every transport or format accepts the same wrappers.

Verify row count and representative values after each run. Include nulls, quoted text and numeric boundaries relevant to the dataset. Check failures with truncated or invalid input separately from successful load timing.

Keep the comparison fair ​

Use fresh test data for each measured load, the same destination schema and the same success checks. Report file sizes, row count, compression choice, host details and repeated elapsed times. Distinguish client-side processing from end-to-end time when measuring both.

Avoid drawing a general performance claim from one dataset. Link the exact format and batch insert behavior used so another developer can reproduce the comparison.