Performance

The engine is designed for a zero-allocation happy path and predictable error costs.

Measured result

Scenario Allocation
Valid model, 5/10/30 properties 0 B/op
Invalid model, 5 errors 968 B
Invalid model, 10 errors 2,104 B
Invalid model, 30 errors 6,024 B
Fail-fast, 5-property model 208 B
Base64 rule 0 B
Localization lookup 0 B

Generated validators are consistently at least as fast as fluent ones on valid paths. Invalid paths are dominated by error construction and are effectively equal.

Diagnostics overhead

Jeninnet.Validation.Diagnostics is opt-in. When ValidationDiagnostics.Sink is null the hot path adds one volatile null check per CompositeValidator call and allocates nothing. When enabled, it creates one short-lived diagnostics scope plus an Activity only when a listener is attached; the histogram/counter use TagList and type/rule-set labels, never messages or values.

Why it is fast

  • ValidationErrorCollector and RootContextData are pooled per thread.
  • Rule selection returns the original rule array when no filters apply.
  • Rules iterate arrays by index; no enumerator allocation.
  • Generated validators emit literal rule construction.
  • Descriptors are frozen and never allocate on repeated Describe().

Measuring your own validators

var validator = new CustomerValidator();
var model = new Customer { /* valid */ };

for (var i = 0; i < 1_000; i++) validator.Validate(model);

var before = GC.GetAllocatedBytesForCurrentThread();
for (var i = 0; i < 1_000; i++) validator.Validate(model);
var after = GC.GetAllocatedBytesForCurrentThread();

Console.WriteLine((after - before) / 1_000.0); // expect 0 in Release

Debug builds can allocate the pooled collector differently; measure in Release.

Benchmarks

The repository publishes machine profile, methodology, and tables in Benchmarks and the allocation contract in Allocation audit.