Benchmark Page is confusing, possibly incorrect?

The benchmark page seems to be claiming that the LocalWeatherReadTest in the source code completes four passes in a total of 10.5 seconds.

The sample code in TinyCsvParserBenchmark() on that page appears to match the code in LocalWeatherReadTest().

I downloaded the exact same 201503hourly.txt file used in the example, 557 MB.

The test took 4 minutes to run, not 10.5 seconds. If I set the degreeOfParallelismList to only have one item in it, it still took a bit over 1 minute to run. Not 10.5 seconds.

Granted we’re not running these tests on the same computer, but I have a really hard time believing your computer is 23 times faster than mine.

Can you shed any light on this? I’m unable to get results that are even slightly close to as fast as what’s being claimed here. The only thing that’s close is the SeqReadTest, which completes in 9-14 seconds for me, depending on what .NET Core runtime I use, but while that test uses the same input file, it doesn’t use any TinyCsvParser code.

[jtmueller]

I’ve been making some pretty good progress with a fork of your parser that I’ve converted to be based on Span<T>. As a result, it only runs on .NET Core 2.1 or better, but I’m seeing some great results so far.

https://gist.github.com/jtmueller/4e6ab27a3fe82c97e0f315c99123c494

[bytefish]

Sounds good! I have a lot of work this week, so I won’t have much time before the weekend. I will merge the BenchmarkDotNet code most probably on the weekend. That means you have all the time you need to create a repository. ☺️