# HPTS 2026 (Day 2 and Day 3)

DevFeed: [HPTS 2026 (Day 2 and Day 3)](<https://devfeed.tech/articles/hpts-2026-day-2-and-day-3-97842.md>)

Original publisher: [Read original article](<https://muratbuffalo.blogspot.com/2026/10/hpts-2026-day-2-and-day-3.html>)

Author: Murat (noreply@blogger.com)

Published: 2026-10-23T16:45:30Z

Content type: article

Language: en

Sources: [Metadata](<https://devfeed.tech/sources/metadata.md>)

Topics: [DuckDB](<https://devfeed.tech/topics/duckdb.md>), [Distributed Systems & Parallel Computing](<https://devfeed.tech/topics/distributed-systems-parallel-computing.md>), [consensus algorithm](<https://devfeed.tech/topics/consensus-algorithm.md>), [Transactions](<https://devfeed.tech/topics/transactions.md>), [Cache](<https://devfeed.tech/topics/cache.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [2026](<https://devfeed.tech/tags/2026.md>), [3](<https://devfeed.tech/tags/3.md>), [about](<https://devfeed.tech/tags/about.md>), [ai](<https://devfeed.tech/tags/ai.md>), [all](<https://devfeed.tech/tags/all.md>), [also](<https://devfeed.tech/tags/also.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [bandwidth](<https://devfeed.tech/tags/bandwidth.md>), [best](<https://devfeed.tech/tags/best.md>), [big-data](<https://devfeed.tech/tags/big-data.md>), [building](<https://devfeed.tech/tags/building.md>), [but](<https://devfeed.tech/tags/but.md>), [capacity](<https://devfeed.tech/tags/capacity.md>), [chair](<https://devfeed.tech/tags/chair.md>), [checksums](<https://devfeed.tech/tags/checksums.md>), [complexity](<https://devfeed.tech/tags/complexity.md>), [compress](<https://devfeed.tech/tags/compress.md>), [compression](<https://devfeed.tech/tags/compression.md>), [compute](<https://devfeed.tech/tags/compute.md>), [hpts](<https://devfeed.tech/tags/hpts.md>), [trip-report](<https://devfeed.tech/tags/trip-report.md>)

## AI overview

The notes trace a recurring systems challenge: moving data and handling operational overhead often constrain performance, energy use, and freshness. The GPU engine Sirius aims to accelerate existing databases without modifying DuckDB, while compressing data to trade abundant GPU compute for scarce memory. Microsoft's DPU approach assigns small accelerators to repetitive tasks such as compression and encryption; the notes also describe runtime selection of data movement strategies based on actual downstream consumption. For object storage, proposals include a net-change diff API, shared append-only logs for concurrent table writes, and a Tesla time-series database querying Parquet directly on S3. Viktor Leis argues that today's S3 designs inherit HDD-driven needs for caching and large reads, and that SSD-based object storage could remove some of this complexity, at higher reported cost. Other talks address reducing Cassandra storage overhead, modeling retry-related metastability, quorum protocols' operational requirements, and the freshness-versus-scalability tradeoffs in lakehouse and HTAP systems.

## Source excerpt

This is the second half of my HPTS 2026 notes. Day 1 was mostly about AI and the importance of specifications. Day 2 and day 3 cover hardware, object storage, failures, consensus, and lakehouses. Session 5: Hardware will save us all (chair: Natassa Ailamaki) The Fastest Way to be the Fastest (Bobbi Yogatama, NVIDIA) GPUs and databases have a love-hate relationship, and Bobbi listed the three reasons: limited GPU memory capacity, the interconnect bottleneck, and engineering complexity. The first two are being fixed by the hardware roadmap. HBM is getting larger and faster. Interconnects and network fabrics are getting faster. But engineering complexity requires some work. No one is eager to rewrite their database to get it work with a GPU. Bobbi introduced Sirius, a GPU-native composable analytics engine. It offers a drop-in accelerator for your existing database, with GPU-native execution underneath. MICE is the design principle: modular, interoperable, composable, extensible. Bobbi showed how Sirius plugs into DuckDB with no modification to DuckDB. The other design lesson from Bobby is to spend compute to save memory. On a GPU, compute is the abundant resource and memory capacity and bandwidth are the scarce ones, so the classic tradeoff needs to flip here. It is best to compress the data, compress everywhere, and operate on the compressed data. The Next Watt Saved Won't Come from a CPU or a GPU (Devashish Purandare, Microsoft) Datacenter power consumption is the bottleneck in building datacenters right now. Where is the power consumed? Tax cycles are 60-80% of all execution. There is datacenter tax: compression, crypto, data movement, memory allocation, protocol and RPC handling. Then there is also system tax: error handling, checksums, filesystems, kernel, STL, networking, multithreading. Unfortunately, no single category dominates, so there is no single high value thing to fix. So how do we fix this? Dev titled his next section: how I learned to stop worrying ab