Django ninja performs better primarily due to relying on pydantic for parsing and validating requests. In a high throughput scenario that's going to be the primary CPU bound area. However usually network or file io is going to be a limiting factor far before CPU.

Django ninja also is build with async in mind fron the start so immediately opens up possibilities that are not possible with DRF.

Seems like as of 4mo ago the maintainers of DRF added async support via a separate module.