Backend
Indexing Designs and Adaptive Data Distribution Optimization for In-Memory Databases on Hybrid DDR--CXL Memory
arXiv cs.DB0 views
arXiv:2610.09414v1 Announce Type: new Abstract: CXL memory expands single-node memory capacity for in-memory databases but has higher latency and lower bandwidth than local DDR. Hybrid DDR--CXL databases require joint indexing and data distribution design. Indexing designs differ in access and migration paths and constrain the placement of indexes and tuples, creating trade-offs in runtime performance, DDR memory efficiency, and system integration complexity. Their performance impact is thus difficult to determine. Indexes and tuples may differ in access characteristics: placing them in the same tier may reduce DDR efficiency, while separate management adds tracking and decision overhead. We propose five indexing designs based on two approaches: treating the two tiers as a unified data space or managing them separately. We analyze their trade-offs and underlying causes and develop adaptive data distribution optimization for single-index designs in which the database explicitly manages distribution. The method manages index objects and tuples separately, reduces metadata overhead through hierarchical hotness tracking and an index object residency policy, and extends benefit-aware admission and randomized eviction to determine and adjust their placement according to each type's expected benefits and memory footprints. We implemented the designs in a hybrid DDR--CXL database prototype and evaluated them using YCSB. The single-index design with direct addressing achieves the best performance under most workloads and system configurations. The dual-index design performs better mainly when DDR capacity is limited or accesses are highly concentrated, and has relatively low integration complexity. Adaptive distribution optimization improves DDR memory efficiency and system performance, enabling single-index designs to achieve up to $1.59\times$ the throughput of their counterparts with non-separated management.
Source:https://arxiv.org/abs/2610.09414PreviousNo Trace, No Claim: Two Contracts for Database AgentsNextCorrespondences as Decisions: JevNexus for Decision-Centric Schema Matching
Related posts
Pod Security Admission audit and warn do not enforce the policy
0dev.to Kubernetes

Best Microservices Testing Tools for Kubernetes
0dev.to Kubernetes
ingress-nginx 退役之後:在臨時叢集實測 Traefik 的 ingress-nginx 相容模式與 Gateway API
0dev.to Kubernetes
Writing Your First Kubernetes Controller in Go: Reconcile, Finalizers, and Mistakes to Avoid
0dev.to Kubernetes
AI Tools Radar, October 2026 edition: 757 open-source AI projects, 51 days of snapshots
0dev.to OpenSource
Lorenz v1.2.2: AppImage updates, winget publishing and CodeQL
0dev.to OpenSource