TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

TurboPFor – DIRECT ACCESS Integer Compression

4 pointsby powturboover 10 years ago

2 comments

nkurzover 10 years ago
Thanks for putting this up! I&#x27;m trying to finish up a paper today on vectorizing VByte decompression, so have been thinking about some of these issues a lot recently.<p>It would be help orient people (like me) if you added more description of the data format you are using for each approach. It&#x27;s difficult reading templatized C at a glance, so I&#x27;m not certain what&#x27;s happening in each format. For example, since the average bit widths for your SimpleV are less than 8, it&#x27;s clearly doing something different than traditional variable byte integer implementations. Nothing wrong with this, but would be helpful to know the details.<p>I&#x27;m mostly with you on the &quot;Realistic and practical benchmark with large integer arrays&quot; part. There are some arguments for variations, though. In particular, reading from memory but decoding to cache can be a more realistic benchmark for search engine applications. Feel free to write email to me or Daniel if you&#x27;d like to try to integrate your benchmarks with ours.
powturboover 10 years ago
TurboPFor - DIRECT ACCESS Integer Compression w&#x2F;o decompressing entire blocks. Instant access to individual compressed array elements X-Times faster.