1987
DOI: 10.1007/bf00263293
|View full text |Cite
|
Sign up to set email alerts
|

Performance evaluation of fork and join synchronization primitives

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
13
0
2

Year Published

1988
1988
2017
2017

Publication Types

Select...
5
2
1

Relationship

0
8

Authors

Journals

citations
Cited by 40 publications
(15 citation statements)
references
References 7 publications
0
13
0
2
Order By: Relevance
“…However, due to the complexity and nontractable characteristics of a TPG, most authors assume an infinite number of processors [GE89, FA83] or assume every task in a TPG runs on a specific processor in the system and every job has the same TPG [BA89,DU87]. In the former case no system delay, caused by waiting in the queue, was considered.…”
Section: Graphmentioning
confidence: 99%
“…However, due to the complexity and nontractable characteristics of a TPG, most authors assume an infinite number of processors [GE89, FA83] or assume every task in a TPG runs on a specific processor in the system and every job has the same TPG [BA89,DU87]. In the former case no system delay, caused by waiting in the queue, was considered.…”
Section: Graphmentioning
confidence: 99%
“…Le temps de réponse du traitement sera le maximum du temps de réponse de chacune des tâches. Dans le FORK-JOIN classique [1,2,3], il y a p tâches avec des arrivées groupées et chacune d'elles est affectée à un des p processeurs. Ici, il y a n tâches et elles peuvent être servies par n'importe lequel des serveurs, quand il est libre.…”
Section: 2 Le N P Fork-joinunclassified
“…Le modèle du système sous forme de réseau de files d'attente conduit à un problème de FORK-JOIN, qui est différent de ceux qui ont été étudiés dans [1], [2], ou [3]. On a un FORK lorsqu'un travail crée n tâches identiques qui seront traitées par p processeurs.…”
unclassified
“…Split-merge (SM) is different from the F/J queueing system in that all of the tasks of an SM request need to complete service before the next SM request can be issued [Duda and Czachrski 1987]. There is a synchronization delay after the completion of the first task until all tasks are completed and before the next SM request can be issued.…”
Section: Introductionmentioning
confidence: 99%