Proceedings of the 2016 International Conference on Management of Data 2016
DOI: 10.1145/2882903.2882934
|View full text |Cite
|
Sign up to set email alerts
|

Scaling Multicore Databases via Constrained Parallel Execution

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
43
0

Year Published

2017
2017
2022
2022

Publication Types

Select...
5
2

Relationship

0
7

Authors

Journals

citations
Cited by 53 publications
(43 citation statements)
references
References 43 publications
0
43
0
Order By: Relevance
“…While pre-execution tries to identify records read and written by transactions without any application semantics, recent work has also shown the benefit of using application semantics explicitly to modify transaction run time with the goal of minimizing, or even avoiding, conflicting operations [3,30,38,44,46]. Given that all CC protocols suffer under highconflict workloads, such techniques, if applicable, will definitely assist in improving the scalability of all architectures.…”
Section: Implications Of Our Analysismentioning
confidence: 99%
“…While pre-execution tries to identify records read and written by transactions without any application semantics, recent work has also shown the benefit of using application semantics explicitly to modify transaction run time with the goal of minimizing, or even avoiding, conflicting operations [3,30,38,44,46]. Given that all CC protocols suffer under highconflict workloads, such techniques, if applicable, will definitely assist in improving the scalability of all architectures.…”
Section: Implications Of Our Analysismentioning
confidence: 99%
“…Two mechanisms are enforced to ensure the serializability. First, because uncommitted data is read, a commit discipline is enforced such that (1) if transaction T operates on uncommitted data from T 0 and T 0 has not committed, T should not commit; and (2) if T 0 aborts, T should also abort [16,36]. Second, dependencies that arise as transactions make conflicting data accesses should be tracked and these dependencies should be enforced by constraining a transaction's subsequent data access.…”
Section: Transaction Pipelinementioning
confidence: 99%
“…In this way, they are able to chop transactions into pieces such that once each piece of transaction code begins to execute, it will not need to delay until the completion of the whole transaction. In the original transaction pipeline approach named IC3 [36], whether two pieces conflict depends on whether they access the same table and one of them contains write. Fine-grained variants are further proposed by regarding two pieces as conflicting pieces if they perform conflicting accesses at runtime [13,16,41].…”
Section: Related Workmentioning
confidence: 99%
See 2 more Smart Citations