Papers for

cloud storage providers

Papers whose findings have a practical use for this group, as judged from the abstract. Open a paper to read what it means in practice.

Private information retrieval with flexible privacy and storage limits

Private Information Retrieval With Arbitrary Privacy Requirements: Introduction and Capacity Results

Abstract: In this paper, we introduce the problem of private information retrieval (PIR) under arbitrary privacy requirements, in a graph-based storage system. This formulation is motivated by the server storage limitations, abundance of data (messages) and heterogeneous data privacy requirements. Under the arbitrary privacy requirement, each message has to be retrieved privately from a pre-specified subset of servers, where the subset always includes the servers storing it. Thus, each server is associated with a privacy set, which pre-specifies the message indices that should be privately retrieved from it. This setting is a generalization of the classical PIR setting, where the required message index needs to be kept private from all servers, i.e., there, the privacy set of each server comprises all message indices. Our setting is also a bridge between the newly formulated local PIR (LPIR) setting and the classical PIR setting, where in the former, the privacy set is exactly the set of stored message indices. In this paper, we derive general lower and upper bounds on the PIR capacity for general graphs, under certain privacy requirements, that capture the essence of both LPIR and classical PIR. Then, we focus on path and cyclic storage graphs under these and more fine-grained settings, for which we derive capacity results for certain cases, and establish lower and upper bounds for others. Their low degree allows for a more in-depth understanding of the new privacy formulation and admits more privacy requirement settings compared to other simple graphs. Finally, we introduce a new graph structure, the pyramid storage graph, to model server storage. Although this graph has never been investigated in the literature in any PIR context, it enjoys a nice symmetric structure for message storage and replication patterns.

Mon 14 SeptInformation TheoryCryptography and SecurityNetworking and Internet Architecture
The gist
The paper deals with how to get data secretly from multiple servers when each data piece needs different privacy rules. It extends traditional methods where every server must not know which data is asked for to cases allowing some servers to know certain queries. The authors study this in systems modeled as networks (graphs) of servers that store and share messages in various ways. They find limits and rules for how efficiently private retrieval can be done depending on these privacy and storage setups. They also introduce a new server structure that had not been studied before but looks balanced and simple.
Open 2609.15875v1

FastPair speeds up GPU string decoding with smarter memory use

FastPair: GPU-Optimized String Decoding

Abstract: Modern data systems compress data at rest and decompress it only when needed to preserve interconnect bandwidth. This design is often inefficient on GPU-based compute platforms because many conventional compression techniques exhibit serial data dependencies that limit GPU parallelism, leaving resources idle. Recent NVIDIA GPUs address this decoding deficiency through the Decompression Engine (DE), an on-die, fixed-function decompression accelerator for general-purpose compression formats such as Deflate, LZ4, and Snappy. Recent work has proposed string codecs that replace frequent substrings with fixed-width codes from a small, trained dictionary, making each code's lookup independent. While these lookups can run in parallel, the resulting scattered reads and short output writes still do not align well with GPU hardware, which handles contiguous memory accesses more efficiently. We present FastPair, a GPU decoder that optimizes the existing dictionary decoding process by reorganizing lookups and assembling decoded substrings for contiguous output writes. On a B300, FastPair decodes ten real-world columns 2.4 to 4.2x faster than the DE, reaching up to 1.6 TB/s.

Mon 14 SeptDatabasesHardware ArchitectureDistributed, Parallel, and Cluster Computing
The gist
Compressing data helps save space but often makes reading it slower, especially on GPUs which work best with parallel tasks. The authors found that current methods for decoding compressed data on GPUs do not fully use the GPU’s strengths due to scattered memory access patterns. They developed FastPair, a decoder that rearranges how data is looked up and stored so the GPU can work faster. This method significantly improves decoding speed on modern GPUs.
Open 2609.15034v1