Implement Rust process benchmarks using Criterion

[Copilot]

Adds Rust benchmarks mirroring the C# benchmarks, following the pattern established in the Go implementation (#25). All benchmarks execute dotnet --help to measure process spawning overhead across different I/O patterns.

Implementation

• 4 benchmark suites covering process execution patterns:

  • no_redirection: Child inherits parent handles (3 benchmarks)
  • discard: Output discarded via Stdio::null() (3 benchmarks)
  • redirect_to_file: Direct OS-level file redirection vs pipe-through (3 benchmarks)
  • redirect_to_pipe: Line-by-line, concurrent, and bulk reading patterns (4 benchmarks)

• Uses Criterion.rs for statistical analysis, HTML reports, and baseline comparisons

• Concurrent I/O handling: Reads stdout/stderr in separate threads to prevent deadlocks when buffers fill

Usage

cd BenchmarksRust
cargo bench                              # Run all benchmarks
cargo bench --bench redirect_to_pipe     # Run specific suite
cargo bench -- pipe                      # Filter by pattern

Reports generated in target/criterion/report/index.html

Documentation

BenchmarksRust/README.md covers:

• Running benchmarks with best practices (release mode, CPU governor settings)
• Filtering by pattern, baseline comparisons, profiling integration
• Output interpretation and troubleshooting
• Assumes reader unfamiliar with Rust ecosystem

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Implement Process benchmarks using rust</issue_title>
<issue_description>Study the C# benchmarks we have in https://github.com/adamsitnik/ProcessPlayground/tree/main/Benchmarks, implement their counterparts using the standard libraries in rust.

Add a short document that explains how to run these benchmarks following all the best practices (like run in Release mode etc). Assume the reader is not familiar with rust.

Context: we did the same for golang #25</issue_description>

<agent_instructions>Run dotnet --help process as part of each benchmark</agent_instructions>

Comments on the Issue (you are @copilot in this section)

• Fixes Implement Process benchmarks using rust #26

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.