Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page
EDBT 2026 Demo / reviewers in the wild / expert

Gunter Krenz

dblp:202/8627 · DBLP profile ↗
← Back
1ranked-venue papers
0as first author
0since 2021 · last 1977
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Databases, data management, data science and information retrieval · 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.

Databases, data mining, and information retrieval
1 paper
Transaction processing and concurrency control · 100%
Computer architecture, parallel and distributed computing, and storage systems
1 paper
Performance modeling and evaluation · 100%

Topics — the 3 heaviest of 3, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Transaction processing and concurrency control
concurrency control		 0.011977
Concurrency in Database Systems - A Simulation Study · SIGMOD Conference 1977
Transaction processing and concurrency control
deadlock		 0.011977
Concurrency in Database Systems - A Simulation Study · SIGMOD Conference 1977
Performance modeling and evaluation
simulation		 0.011977
Concurrency in Database Systems - A Simulation Study · SIGMOD Conference 1977

Methods — techniques the papers use, named apart from their topics

simulation · 0.0
YearPublicationVenuePosition
1977 Concurrency in Database Systems - A Simulation Study
abstract
A simulation model of concurrent updates in a database system is presented. This model is used, to answer the following questions: How frequent are deadlocks in certain environments? What about concurrency and wait-time of user processes as a function of the synchronization method used? In case of a deadlock what are useful criteria to select the process to be rolled back? How many checkpoints make sense?
Rudolf Munz, Gunter Krenz
 SIGMOD Conference2