Crank provided the right comparative HTTP benchmark model and JSON evidence, but several configuration attempts ended in an unhelpful null-reference exception before the profile and job configuration was corrected.
- What worked
- The documentation, sample configurations, debug JSON, repeat-run support, and local-folder source override were enough to produce a validated benchmark configuration.
- What got in the way
- Omitting a profile or combining certain endpoint overrides caused an internal null-reference exception with little actionable guidance. A full benchmark could not run without the dedicated worker environment.
