<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>ParPaRaw: Massively Parallel Parsing of Delimiter-Separated Raw Data · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/1905.13415/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/1905.13415/feed.xml" rel="self" type="application/rss+xml" /><item><title>ParPaRaw: Massively Parallel Parsing of Delimiter-Separated Raw Data — mentioned by criticaltinker</title><link>https://news.ycombinator.com/item?id=29722331</link><guid isPermaLink="false">urn:hackerpapers:mention:1905.13415:29722331</guid><pubDate>Wed, 29 Dec 2021 05:56:50 GMT</pubDate><description>&lt;p&gt;DFAs and NFAs may seem like academic novelties but they are amazingly powerful for certain problems. For example, naively searching a string of length N for P different substrings will yield an algorithm that has roughly O(N * P) worst case time complexity. But implementing that algorithm as a DFA yields an efficient construction that has O(N) worst case time complexity. This results in considerable speedups for complex pattern recognition tasks on large inputs, and yields other useful properties. As a real world example, a CSV file can be parsed in parallel on a GPU by using a DFA based…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1905.13415/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.DB</category></item><item><title>ParPaRaw: Massively Parallel Parsing of Delimiter-Separated Raw Data — mentioned by ejbs</title><link>https://news.ycombinator.com/item?id=20302426</link><guid isPermaLink="false">urn:hackerpapers:mention:1905.13415:20302426</guid><pubDate>Fri, 28 Jun 2019 08:22:08 GMT</pubDate><description>&lt;p&gt;&amp;gt; They did not include the time it took to transfer the input file from memory to the GPU To give some context: PCIe 3.0 x16 achieves about 11-12 GB/s. So, transfers for benchmarked 53MB file would add ~4.8 ms (per direction, assuming pinned host memory) Now, they could also pursue a streaming approach, processing in &amp;quot;micro-batches&amp;quot;. I.e., pipelining input transfers (HOST-&amp;gt;GPU), GPU-based processing, and transfer of results (GPU-&amp;gt;HOST), as pursued by [1] (disclaimer: I&amp;#x27;m a co-author). This lower&amp;#x27;s processing latency. Since the interconnect is full-duplex, it would just limit the processing…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1905.13415/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.DB</category></item></channel></rss>
