<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Relational Memory: Native In-Memory Accesses on Rows and Columns · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2109.14349/</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/2109.14349/feed.xml" rel="self" type="application/rss+xml" /><item><title>Relational Memory: Native In-Memory Accesses on Rows and Columns — mentioned by rwmj</title><link>https://news.ycombinator.com/item?id=38725043</link><guid isPermaLink="false">urn:hackerpapers:mention:2109.14349:38725043</guid><pubDate>Thu, 21 Dec 2023 18:56:40 GMT</pubDate><description>&lt;p&gt;Red Hat supported a lot of research into this and there&amp;#x27;s some really interesting stuff, but nothing that is very compelling for commercial use. What uses do you have in mind? To my mind the more interesting stuff are the PCIe FPGA boards like https://www.xilinx.com/products/boards-and-kits/alveo/u200.h... One particularly interesting research project was using the FPGA fabric to remap addresses, allowing database tables to be &amp;quot;virtually&amp;quot; rearranged (eg. making a row-major data source into a column-major source for easier searching). https://disc.bu.edu/papers/edbt23-relational-memory…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2109.14349/"&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>Relational Memory: Native In-Memory Accesses on Rows and Columns — mentioned by rwmj</title><link>https://news.ycombinator.com/item?id=37775919</link><guid isPermaLink="false">urn:hackerpapers:mention:2109.14349:37775919</guid><pubDate>Thu, 05 Oct 2023 07:54:30 GMT</pubDate><description>&lt;p&gt;But the bet was customers would buy Xeons with an FPGA block that would &amp;quot;do magic&amp;quot;. What magic it would do and how you&amp;#x27;d program it in a sane way was never specified in great detail. In any case for those that really want this it turns out you can put the FPGA on the end of a regular PCIe link and get all the same benefits. Edit: By the way there is some niche research of the FPGA in core (which don&amp;#x27;t work if the FPGA is over PCIe). This paper describes a way to rearrange memory using a programmable FPGA-based memory controller to optimize database table accesses…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2109.14349/"&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>Relational Memory: Native In-Memory Accesses on Rows and Columns — mentioned by rwmj</title><link>https://news.ycombinator.com/item?id=34063245</link><guid isPermaLink="false">urn:hackerpapers:mention:2109.14349:34063245</guid><pubDate>Tue, 20 Dec 2022 08:40:42 GMT</pubDate><description>&lt;p&gt;Something similar in this paper, putting an FPGA between the processor and DRAM so you can arbitrarily remap bits of it: https://arxiv.org/abs/2109.14349&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2109.14349/"&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>Relational Memory: Native In-Memory Accesses on Rows and Columns — mentioned by rwmj</title><link>https://news.ycombinator.com/item?id=33505361</link><guid isPermaLink="false">urn:hackerpapers:mention:2109.14349:33505361</guid><pubDate>Mon, 07 Nov 2022 13:14:58 GMT</pubDate><description>&lt;p&gt;This paper is a slightly different approach to a similar problem: https://arxiv.org/abs/2109.14349 They are inserting an FPGA fabric between standard CPUs and standard DDR RAM, allowing the memory to be reorganized on the fly. For example you can flip columns and rows in arrays, or turn ordinary row-oriented databases into column-first databases. I think all these approaches have a problem that you end up having to throw away all existing software to take advantage of them.&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2109.14349/"&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>Relational Memory: Native In-Memory Accesses on Rows and Columns — HN submission</title><link>https://news.ycombinator.com/item?id=33248923</link><guid isPermaLink="false">urn:hackerpapers:submission:2109.14349:33248923</guid><pubDate>Tue, 18 Oct 2022 15:33:53 GMT</pubDate><description>&lt;p&gt;Using an FPGA to transform rows to columns on in-memory databases&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;7 points; 0 discussion replies on HN. &lt;a href="https://hackerpaper.kaipfister.de/p/2109.14349/"&gt;Paper and source history&lt;/a&gt;. A submission is not an endorsement.&lt;/p&gt;</description><category>cs.DB</category></item><item><title>Relational Memory: Native In-Memory Accesses on Rows and Columns — mentioned by belter</title><link>https://news.ycombinator.com/item?id=28741293</link><guid isPermaLink="false">urn:hackerpapers:mention:2109.14349:28741293</guid><pubDate>Sun, 03 Oct 2021 23:02:16 GMT</pubDate><description>&lt;p&gt;&amp;quot;Analytical database systems are typically designed to use a column-first data layout that maps better to analytical queries of access patterns. This choice is premised on the assumption that storing data in a row-first format leads to accessing unwanted fields; moreover, transforming rows to columns at runtime is expensive. On the other hand, new data items are constantly ingested in row-first form and transformed in the background to columns to facilitate future analytical queries. How will this design change if we can always access only the desired set of columns? In this paper, to address…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2109.14349/"&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>Relational Memory: Native In-Memory Accesses on Rows and Columns — HN submission</title><link>https://news.ycombinator.com/item?id=28741292</link><guid isPermaLink="false">urn:hackerpapers:submission:2109.14349:28741292</guid><pubDate>Sun, 03 Oct 2021 23:02:16 GMT</pubDate><description>&lt;p&gt;Relational Memory: Native In-Memory Accesses on Rows and Columns&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;3 points; 1 discussion reply on HN. &lt;a href="https://hackerpaper.kaipfister.de/p/2109.14349/"&gt;Paper and source history&lt;/a&gt;. A submission is not an endorsement.&lt;/p&gt;</description><category>cs.DB</category></item></channel></rss>
