2015
DOI: 10.1007/978-3-319-27308-2_43
|View full text |Cite
|
Sign up to set email alerts
|

Quantifying the Performance Impact of Graph Structure on Neighbour Iteration Strategies for PageRank

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
8
0

Year Published

2017
2017
2024
2024

Publication Types

Select...
2
2
1

Relationship

0
5

Authors

Journals

citations
Cited by 7 publications
(8 citation statements)
references
References 14 publications
0
8
0
Order By: Relevance
“…However, the use of the static deployment model has negative consequences. Conceptually, graph applications are a poor fit for static, fixed-size infrastructure, as they have often iterative, but highly irregular workloads [3]. Previous techniques do not focus on a dynamic model of deployment, where infrastructure can grow and shrink to match the needs of the graph-processing application.…”
Section: Problem Statement and Conceptual Contributionmentioning
confidence: 99%
See 1 more Smart Citation
“…However, the use of the static deployment model has negative consequences. Conceptually, graph applications are a poor fit for static, fixed-size infrastructure, as they have often iterative, but highly irregular workloads [3]. Previous techniques do not focus on a dynamic model of deployment, where infrastructure can grow and shrink to match the needs of the graph-processing application.…”
Section: Problem Statement and Conceptual Contributionmentioning
confidence: 99%
“…Typically, when making a case for elasticity [9] in graph processing, only graph-related metrics are considered, such as active vertices, or messages exchanged per super-step. Many complementary studies present an analysis on how the number of active vertices affects the algorithm efficiency: directionoptimizing BFS [10] is a technique entirely motivated by the variable number of active edges per iteration; Mizan [11] analyzes runtime per iteration and addresses the large imbalance; GraphReduce [12] leverages the observed variability in the number of active vertices (frontier size) for two datasets and three algorithms; high workload imbalance appears even between multiple designs and implementations of the same algorithm running the same workload [3]; etc. In contrast, we also analyze the impact of workload imbalance on the consumption of system-level resources.…”
Section: Problem Statement and Conceptual Contributionmentioning
confidence: 99%
“…GraphReduce [28] finds large variability in the number of active vertices (frontier size) for two datasets and three algorithms. High workload imbalance appears even between multiple designs and implementations of the same algorithm running the same workload [17]. In comparison, in this section we further analyze the impact of workload imbalance on the consumption of system-level resources.…”
Section: Variability In Graph Processingmentioning
confidence: 99%
“…The use of the static deployment model has negative consequences. Conceptually, graph applications are a poor fit for static, fixed-size infrastructure, because they have often iterative, but highly irregular workloads [5], [7], [17]. Pragmatically, even experts face difficult choices based on empirical approaches to estimate the size of the needed infrastructure; there are serious consequences when the choice is inaccurate, ranging from system-wide crashing when resources are underprovisioned [18], to possibly high resource waste and operational costs when the system is over-provisioned.…”
Section: Introductionmentioning
confidence: 99%
“…Although many works utilize GPU to accelerate the computations of PageRank, former study rarely focuses on speeding up local PageRank problem through GPU. Previous work utilizes GPU to speed up local PageRank computations in Lai et al However, it is still an issue that the dangling vertices restrict scope of usage.…”
Section: Introductionmentioning
confidence: 99%