Recently I have been seeing some articles related to the performance, specially for AutoMapper vs Mapster.

So I decided to run some performance tests and share it with the community.

Files used for test

Person.cs will be the source class.

PersonDTO.cs will be the destination class.

So then I ran a big loop on the Map method for both AutoMapper and Mapster.

The first loop is mapping using AutoMapper.

The second loop is mapping using Mapster.

The third loop is a manual test.

The results

For each loop I was counting the time using Stopwatch class.

So the results shows the Mapster is faster than AutoMapper and having no mapper library is slightly faster.

Having no mapping library could potentially increase your maintenance and this is prone to go wrong.

Testing using Benchmark library

Benchmark Results

Conclusion:

The results confirm that Mapster is indeed faster than AutoMapper. However, No Mapper outperforms both libraries in terms of raw speed. The decision ultimately depends on your project’s requirements:

• Use No Mapper for maximum performance and control.
• Use Mapster for a good balance of performance and convenience.
• Use AutoMapper for ease of use and community support, especially in less performance-critical scenarios.