Compares the old (master branch) vs new (universal branch) WebSocket implementations across latency, throughput, GC allocations, frame time impact, and burst handling.

cd benchmarks/server
npm install
node index.js

Server listens on ws://localhost:3000. Set PORT env var to change.

cd benchmarks/ConsoleRunner
dotnet run -c Release

This runs the old vs new comparison without opening Unity and is useful for quick iteration on the benchmark harness.

python3 benchmarks/compare_results.py \
  /path/to/benchmark_old_sync.csv \
  /path/to/benchmark_old_sync_2.csv \
  /path/to/benchmark_new_sync.csv \
  /path/to/benchmark_new_sync_2.csv \
  --baseline old \
  --candidate new

Helpful filters:

• --benchmarks Throughput_Recv FrameTime_Dispatch Burst
• --metrics msgs_per_sec avg_ms p95_ms p99_ms total_time_ms
• --payloads 32 256 1024 8192 65536

The benchmark assets now include BenchmarkBatchRunner.RunSyncContextBenchmarks, which creates an empty scene, runs receive throughput + frame time + burst tests, writes a CSV, and exits Unity in batchmode.

Useful command-line args:

• -benchmarkImplementation old|new
• -benchmarkOutput benchmark_results.csv
• -benchmarkThroughputDuration 5
• -benchmarkPayloadSizes 32,256,1024,8192,65536

1. Create a new Unity project (2019.4+)
2. Copy BenchmarkOld/Assets/ contents into your project's Assets/ folder
3. Create an empty scene and add an empty GameObject with the BenchmarkRunner component
4. Configure parameters in the Inspector (defaults are reasonable)
5. Ensure implementationName is set to "old"
6. Press Play

1. Create a new Unity project (2019.4+)
2. Copy BenchmarkNew/Assets/ contents into your project's Assets/ folder
3. Create an empty scene and add an empty GameObject with the BenchmarkRunner component
4. Ensure implementationName is set to "new"
5. Press Play

CSV files are written to Application.persistentDataPath/benchmark_results.csv. The path is logged to the Unity Console at startup.

CSV columns: timestamp, implementation, benchmark, metric, value, payload_size

Each benchmark runs across payload sizes: 32B, 256B, 1KB, 8KB, 64KB (configurable).

The Unity BenchmarkRunner can also selectively enable send / receive / bidirectional throughput runs through:

• runThroughputSend
• runThroughputReceive
• runThroughputBidirectional

The benchmark server responds to:

• Binary messages: Echoed back immediately
• flood:<count>:<size>: Send count binary messages of size bytes
• flood_continuous:<size>: Continuously flood binary messages of size bytes until stopped
• flood_stop: Stop a continuous flood and send a flood_stopped text signal
• sink:start:<sessionId>: Stop echoing binary traffic for that connection (used by send-throughput tests)
• burst:<count>:<size>: Send count messages + "burst_done" text signal
• Text messages: Echoed back

benchmarks/
├── server/              # Node.js WebSocket echo/flood server
│   ├── package.json
│   └── index.js
├── BenchmarkOld/        # Old implementation (master branch)
│   └── Assets/
│       ├── WebSocket/
│       │   └── WebSocket.cs         # Monolithic 848-line file from master
│       └── Benchmark/
│           ├── BenchmarkRunner.cs   # Orchestrator MonoBehaviour
│           ├── LatencyBench.cs
│           ├── ThroughputBench.cs
│           ├── GCAllocBench.cs
│           ├── FrameTimeBench.cs
│           ├── BurstBench.cs
│           ├── BenchmarkStats.cs    # Percentile/stats calculator
│           └── BenchmarkLogger.cs   # CSV + console output
├── BenchmarkNew/        # New implementation (universal branch)
│   └── Assets/
│       ├── NativeWebSocket/
│       │   ├── IWebSocket.cs
│       │   ├── WebSocket.cs
│       │   └── WebSocketTypes.cs
│       └── Benchmark/
│           └── ... (identical scripts)
└── README.md

The benchmark C# scripts are identical in both projects. Only the WebSocket implementation differs.