[nh2]

For clarification, does "mib/s" mean "Mbit/s" (since lowercase b usually stands for bits, and uppercase B usually for Bytes)?

If yes, how comes log processing runs at only so low throughput in general?

That is not to talk down your achievements (as per your benchmark page, you do better than similar projects in terms of throughput), but I'm genuinely curious why modern machines that have 40 Gbit/s memory bandwidth are capped at (in your case) 76.7Mbit/s. What's the bottleneck?

[amanzi]

The capitalisation is confusing, but "Mi" means "mebi" - either Mib for mebibits or MiB for mebibytes. The correct term for 1024 * 1024 bits is a Mib, and, 1024 x 1024 x8 bits is a MiB.

[nh2]

That is correct, but it doesn't answer the question whether it's Bytes or bits (which makes an 8x difference).

Given that the reported values don't care about the "m" (which means "milli" -- clearly doesn't make sense for bytes), I don't think we can rely on the casing of the "b" to tell us the answer.

[nh2]

I've asked it here now: https://github.com/timberio/vector/issues/568

[binarylogic]

Ah, I'm amazed that I did not know this. I just updated everything to use MiB. Thanks for pointing that out.