3 ms·
The benchmarks claim it searched 35GB of data in 0.6s. I must not be understanding what that means, because that's nearly 60 GB/second. The web page notes every
by NelsonMinar 11y ago
The benchmarks claim it searched 35GB of data in 0.6s. I must not be understanding what that means, because that's nearly 60 GB/second. The web page notes everything's cached, so there's no disk I/O. But isn't 60 GB/second about the bandwidth of consumer RAM?
- eternauta3k 11y agoYou don't have to look at all the data, if the prefix of the search doesn't match then you can skip ahead for some search patterns.
- tedunangst 11y agoThe pattern only had a nine byte prefix, that's not a lot of skipping. And it's far less than a cache line.
- glandium 11y agoAnd the only way to read 35GB of data at 60GB/s is to have it all in RAM in the first place. That's a lot of RAM to have.