We are checking the asp.net core 2.0 performance and found out this:
Asp.Net core application hosted/running under IIS using ASP.NET Core Module performance is worst in about 60% then Full frame work. Second case: same application self-hosted and using IIS as reverse proxy with URL rewrite module increase performance in about 20% better than Full FW. FW 4.6.1.
Another aspect that have major impact on performance is logging. Insure that application under test doesn't write debug/info log to console (by default). Log configuration under test should not log info and debug.
Second problem that we deal with is: Asp.net core performance issue when consuming WCF service. We found out that in current version 2.0.5 the performance vs Asp.Net FW worse in about 70% and what is more important have a huge error rate (23%) of all test.
The problem here is laying in port exhaustion. MS recommend to increase the number of ephemeral ports. Increasing then number of ephemeral port improved the error rate, but not solved the problem. Our test setup: Asp.Net core2.0 and Asp.Net FW apps with WEB Api controller that return some string Load test: start with 5 user increase by 5 every 30 seconds. Test is running for 8 minutes
Read out the ASP.Net Core 2.1 RoadMap. I think MS aware for those issues and they will fix major issues in 2.1 release. We are waiting for it.