Demo Data from VLDB 2026 / reviewers in the wild / expert
Mark Sweiger
dblp:39/2048
· DBLP profile ↗
1ranked-venue papers
0as first author
0since 2021 · last 1990
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Systems, architecture and hardware · 1Software engineering, systems software and programming languages · 1
Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.
| Computer architecture, parallel and distributed computing, and storage systems
1 paper |
Performance modeling and evaluation · 30% Parallel and multicore computing · 30% Processor architecture and microarchitecture · 30% |
Topics — the 4 heaviest of 4, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Processor architecture and microarchitecture › multiprocessor architecture
bus-based multiprocessor |
0.0 | 1 | 1990 | Performance of an OLTP Application on Symmetry Multiprocessor System · ISCA 1990 |
Parallel and multicore computing › multiprocessor system
shared-memory multiprocessor |
0.0 | 1 | 1990 | Performance of an OLTP Application on Symmetry Multiprocessor System · ISCA 1990 |
Performance modeling and evaluation
workload characterization |
0.0 | 1 | 1990 | Performance of an OLTP Application on Symmetry Multiprocessor System · ISCA 1990 |
Memory systems › cache
cache performance |
0.0 | 1 | 1990 | Performance of an OLTP Application on Symmetry Multiprocessor System · ISCA 1990 |
Methods — techniques the papers use, named apart from their topics
benchmarking · 0.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 1990 | Performance of an OLTP Application on Symmetry Multiprocessor SystemabstractSequent's Symmetry Series is a bus-based shared-memory multiprocessor. System performance in an OLTP relational database application was investigated using the TP1 benchmark. System performance was tested with fully-cached benchmarks and with scaled benchmarks. In fully-cached tests, the entire database fits inside main memory. In scaled tests, the database is larger than available memory. In the fully-cached benchmark, performance was initially limited by bus saturation. The cause was the transfer of process context from processor to processor. This was eliminated by assigning each process to a processor. Processor affinity was combined with reductions in message-passing within the database. Throughput was dramatically improved. The scaled tests were I/O bound. This bottleneck can be eliminated by connecting more disk drives, or by increasing the main memory size. Shreekant S. Thakkar, Mark Sweiger |
ISCA | 2 |