For an API server:

• Sync: execution waits/blocks for the operation.
• Async: execution can continue while waiting for I/O.
• Concurrent: multiple operations make progress over overlapping time.
• Parallel: multiple operations execute simultaneously.

On a single CPU core, can multiple API requests be async + concurrent but not parallel when one is waiting for I/O and another is executing?

And does SMT/Hyper-Threading change this distinction?

Single-threaded JS execution ≠ single-threaded runtime.

How do you explain the distinction?

Hey NestJS developers,

If you've profiled high-throughput NestJS APIs, you've probably noticed that payload serialization and validation can become a significant CPU hotspot.

The default ValidationPipe performs two reflection-heavy passes: one with class-transformer to create the DTO instance, and another with class-validator to validate it. Those repeated reflection and property-iteration steps can hurt V8 optimizations by disrupting hidden classes and inline caches.

I built fast-class-transformer, a zero-dependency alternative that uses a JIT-compiled FastMap() decorator.

Instead of performing reflection on every request, it analyzes your DTO decorators once during application startup and generates a specialized JavaScript function for that DTO. Every request then executes that compiled mapper, combining mapping and validation into a single pass.

Traditional pipeline

Plain JSON → Reflection Mapper → DTO Instance → Reflection Validator → Validated Output

JIT pipeline

Plain JSON → Single-Pass JIT Function (Map + Validate) → Validated Output

Benchmarks

Intel i5-12500H • Bun 1.3.0 • 100k iterations (Inputs rotated across 1,024 payloads)

• Standard NestJS ValidationPipe: 2.97 µs/iter
• JIT FastMap(): 45.98 ns/iter (64× faster)

It also supports familiar decorators such as Expose, Type, Transform, and more.

GitHub repository and benchmark methodology are in the comments.