2017
DOI: 10.1007/978-3-319-52709-3_23
|View full text |Cite
|
Sign up to set email alerts
|

The Contention Avoiding Concurrent Priority Queue

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
7
0

Year Published

2018
2018
2021
2021

Publication Types

Select...
5

Relationship

0
5

Authors

Journals

citations
Cited by 6 publications
(7 citation statements)
references
References 17 publications
0
7
0
Order By: Relevance
“…We believe that further practical improvements could be possible by better avoiding conflicting queue accesses of the sticky variant even when few queues are used. It would also be interesting to make MultiQueues contention aware to achieve higher quality and more graceful degradation than the simple binary switch between local and global access used in the CAPQ [21].…”
Section: Discussionmentioning
confidence: 99%
See 2 more Smart Citations
“…We believe that further practical improvements could be possible by better avoiding conflicting queue accesses of the sticky variant even when few queues are used. It would also be interesting to make MultiQueues contention aware to achieve higher quality and more graceful degradation than the simple binary switch between local and global access used in the CAPQ [21].…”
Section: Discussionmentioning
confidence: 99%
“…We compare the MultiQueue to the following state-of-the-art concurrent priority queues. CAPQ [21] dynamically detects contention to switch from using a shared skip list based priority queue to thread-local buffers. We used the implementation found in the Github repository of the k-LSM 3 for all of the above priority queues.…”
Section: Comparison With Other Approachesmentioning
confidence: 99%
See 1 more Smart Citation
“…A parallel research thread has been on providing efficient relaxed schedulers with guarantees on the maximum amount of priority rank relaxation, e.g. [6,23,26,24]. Of these, arguably the most popular design is the Multi-Queue [23], which works roughly as follows: given n threads, we instantiate m ≥ n concurrent priority queues, which will store tasks.…”
Section: Introductionmentioning
confidence: 99%
“…A standard example is parallelizing Dijkstra's single-source shortest paths (SSSP) algorithm, e.g. [3,22,20]: the scheduler can retrieve vertices in relaxed order without breaking correctness, as the distance at each vertex is guaranteed to eventually converge to the minimum. The trade-off is between the performance gains arising from using simpler, more scalable schedulers, and the loss of determinism and the wasted work due to relaxed priority order.…”
mentioning
confidence: 99%