PSWriteOffice Performance Evidence

PSWriteOffice uses the PSPublishModule/PowerForge benchmark runner so scenario rotation, cleanup, result validation, and report generation share one implementation. Excel is compared with PowerShell-facing workbook tools; CSV is compared with native PowerShell CSV handling.

What is compared

• Every Excel reader receives the same PSWriteOffice-generated workbook shape.
• Unsupported or semantically different competitor lanes are marked Skipped, not treated as wins.
• CSV comparisons include object, DataTable, compression, wide-column, quoted-field, and dbatools-shaped workloads.
• Output validation happens inside the scenario contract. Managed cleanup runs after setup and outside the timed operation.
• Results are local snapshots with retained run context, not promises for every machine or workload.

Run the smoke suites

From a PSWriteOffice checkout with a sibling OfficeIMO source tree:

$env:OfficeIMORoot = (Resolve-Path ..\OfficeIMO).Path

pwsh -NoLogo -NoProfile -ExecutionPolicy Bypass `
    -File .\Benchmarks\Compare-ExcelPerformance.ps1 `
    -Suite Smoke

pwsh -NoLogo -NoProfile -ExecutionPolicy Bypass `
    -File .\Benchmarks\Compare-CsvPerformance.ps1 `
    -Suite Smoke

Use -Plan to inspect the selected scenarios without running them. Use -UpdateReadme only when intentionally recording a new result snapshot.

Selected committed results

These rows are examples from the current committed PSWriteOffice benchmark report. They deliberately include a result where native PowerShell is faster.

Do not choose a package from one row. Run the scenario matching your row count, schema, compression, formatting, and validation needs on infrastructure close to production.

Open the complete benchmark source and generated tables or return to the OfficeIMO benchmark hub.