Update Linux plaintext pipelining results

This was based on perf testing done January 13th with the same wrk
params as before. I'm unsure what the CPU utilization was at the time.

Author: halter73

README.md

@@ -133,7 +133,7 @@ Like the Plain Text scenario above but with HTTP pipelining enabled at a depth o
 | NodeJS | perfsvr | 147,554 | 32 threads, 256 connections | The actual TechEmpower NodeJS app | CPU is 100%, almost exclusively in user mode |
 | NodeJS | perfsvr2 (Linux) | 173,641 | 32 threads, 512 connections | The actual TechEmpower NodeJS app | CPU is 100% |
 | ASP.NET Core on Kestrel | perfsvr | 1,188,521 | 32 threads, 256 connections | Middleware class, multi IO thread | CPU is 100% |
-| ASP.NET Core on Kestrel | perfsvr2 (Linux) | 409,856 | 32 threads, 256 connections | Middleware class, single IO thread | CPU is 75% |
+| ASP.NET Core on Kestrel | perfsvr2 (Linux) | 928,023 | 32 threads, 256 connections | Middleware class, single IO thread | |
 | Scala | perfsvr | 1,514,942 | 32 threads, 1024 connections | The actual TechEmpower Scala plaintext app | CPU is 100%, 70% in user mode |
 | Netty | perfsvr | 2,808,515 | 32 threads, 256 connections | The actual TechEmpower Netty app | CPU is 100% |