D
David B. Lomet
Researcher at Microsoft
Publications - 155
Citations - 7043
David B. Lomet is an academic researcher from Microsoft. The author has contributed to research in topics: Tree (data structure) & Distributed transaction. The author has an hindex of 47, co-authored 155 publications receiving 6700 citations. Previous affiliations of David B. Lomet include University of Extremadura.
Papers
More filters
Proceedings ArticleDOI
The Bw-Tree: A B-tree for new hardware platforms
TL;DR: The architecture and algorithms for the Bw-tree are described, focusing on the main memory aspects, which achieves its very high performance via a latch-free approach that effectively exploits the processor caches of modern multi-core chips.
Journal ArticleDOI
The hB-tree: a multiattribute indexing method with good guaranteed performance
David B. Lomet,Betty Salzberg +1 more
TL;DR: This work presents results that guarantee that the hB-tree copes well with arbitrary distributions of keys, decent storage utilization, reasonable size index terms, and good search and insert performance.
Journal ArticleDOI
Access methods for multiversion data
David B. Lomet,Betty Salzberg +1 more
TL;DR: The splitting policies have been changed to reduce redundancy in the structure—the option of pure key splits as in B+-trees and a choice of split times for time-based splits enable this performance enhancement.
Patent
Database computer system with application recovery and dependency handling write cache
TL;DR: In this paper, a database computer system and a method for making applications recoverable from system crashes is described, where the application state (i.e., address space) is treated as a single object which can be atomically flushed in a manner akin to flushing individual pages in database recovery techniques.
Patent
Client-server computer system with application recovery of server applications and client applications
David B. Lomet,Gerhard Weikum +1 more
TL;DR: In this paper, the server runs a resource manager to log operations and data pages in a manner that enables application and database recovery, and the server's resource manager creates a stable log file that can be used to help recover the client-side application in the event of a system crash.