Parsing integers quickly with AVX-512

Re:Parsing integers quickly with AVX-512 by benj111 on Monday September 25, 2023 @03:49AM (#37640705)

I agree with the parent, but from a different angle.

If you need to parse integers so quickly, why are you storing them as decimal strings?

If you're dealing with a massive CSV why not just compile to a more easily parsable format ahead of time?

[ Parent | on HN ]

Re:Parsing integers quickly with AVX-512 by anonymoushn on Monday September 25, 2023 @04:50AM (#37641030)

Because we receive them over the wire as decimal strings.

[ Parent | on HN ]

Re:Parsing integers quickly with AVX-512 by benj111 on Monday September 25, 2023 @06:52AM (#37641804)

Define over the wire here then.

The article mentions 0.8gb/s to 1.8gb/s throughput.

If youre downloading something off the internet, the bottleneck isn't going to be converting the strings to ints.

Further if you're downloading that much data, it suggests even more that you should be using a more space efficient representation.

[ Parent | on HN ]

Re:Parsing integers quickly with AVX-512 by anonymoushn on Monday September 25, 2023 @07:11AM (#37641970)

For trading we focus on latency rather than throughput.

We cannot really accomplish much by telling a bunch of other companies to change the format they use to send data to all of their customers.

[ Parent | on HN ]

Re:Parsing integers quickly with AVX-512 by benj111 on Monday September 25, 2023 @08:00AM (#37642356)

Ah ok, the post didn't mention trading, and that use case didn't occur to me.

[ Parent | on HN ]