Proceedings of the Fifth International Workshop on Graph Data-Management Experiences &Amp; Systems 2017
DOI: 10.1145/3078447.3078452
|View full text |Cite
|
Sign up to set email alerts
|

Can Modern Graph Processing Engines Run Concurrent Queries Efficiently?

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
4
0

Year Published

2018
2018
2024
2024

Publication Types

Select...
4
1

Relationship

1
4

Authors

Journals

citations
Cited by 5 publications
(4 citation statements)
references
References 10 publications
0
4
0
Order By: Relevance
“…In order to compare the estimates for the parallel and the sequential case, we use the total cost per vertex 𝐶 total (𝑇 , 𝑀). This cost is the sum of the costs to process the vertex itself and the cost of its share of edges and the newly found vertices, as shown in Equation (8).…”
Section: Cost Modelmentioning
confidence: 99%
See 1 more Smart Citation
“…In order to compare the estimates for the parallel and the sequential case, we use the total cost per vertex 𝐶 total (𝑇 , 𝑀). This cost is the sum of the costs to process the vertex itself and the cost of its share of edges and the newly found vertices, as shown in Equation (8).…”
Section: Cost Modelmentioning
confidence: 99%
“…For multi-query execution, in the following referred to as number of concurrent queries, the problem worsens as an additional dimension is added, which is to select a schedule with the right amount and set of queries to be processed concurrently. In one of our previous works we showed that multi-query execution using simply multiple parallel engines at the same time can degrade performance [8]. To overcome this, given enough concurrent queries ready for execution, a promising option might be to process each query internally sequential (intra-query), what minimizes synchronization overhead, and thereby sourcing the required degree of parallelism from many concurrent queries (inter-query).…”
Section: Introductionmentioning
confidence: 99%
“…While CGraph processes FPP queries by iterations, ForkGraph processes FPP queries in the partitionlevel granularity, leveraging work-efficient sequential executions. Hauck et al [29] motivate the experimental studies of processing concurrent queries based on the multi-user setups in classic relational enterprise database environments or web-scale environments. They study the inter-and intra-parallelism of handling different types of graph queries by assigning different threads to different instances of Galios [45].…”
Section: Related Workmentioning
confidence: 99%
“…All of the presented approaches support only a single, batch processing query rather than multiple, interactive graph queries. Hauck et al [14] provided experimental evidence that single-query graph systems do not scale well in a multi-query environment.…”
Section: Related Workmentioning
confidence: 99%