2007 IEEE International Parallel and Distributed Processing Symposium 2007
DOI: 10.1109/ipdps.2007.370349
|View full text |Cite
|
Sign up to set email alerts
|

Capacity Sharing and Stealing in Dynamic Server-based Real-Time Systems

Abstract: Abstract

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
19
0

Year Published

2008
2008
2012
2012

Publication Types

Select...
3
2
1

Relationship

1
5

Authors

Journals

citations
Cited by 9 publications
(19 citation statements)
references
References 18 publications
0
19
0
Order By: Relevance
“…The Capacity Sharing and Stealing (CSS) scheduler [9] proposes to handle overloads with additional capacity that is available from two sources: (i) by reclaiming unused allocated capacity when jobs complete in less than their budgeted execution time; and (ii) by stealing allocated capacities to nonisolated servers used to schedule sporadic best-effort jobs. The integration of the CSS scheduler into the CooperatES framework is discussed in detail in [54].…”
Section: Related Workmentioning
confidence: 99%
See 1 more Smart Citation
“…The Capacity Sharing and Stealing (CSS) scheduler [9] proposes to handle overloads with additional capacity that is available from two sources: (i) by reclaiming unused allocated capacity when jobs complete in less than their budgeted execution time; and (ii) by stealing allocated capacities to nonisolated servers used to schedule sporadic best-effort jobs. The integration of the CSS scheduler into the CooperatES framework is discussed in detail in [54].…”
Section: Related Workmentioning
confidence: 99%
“…This paper reformulates the distributed resource allocation problem as an anytime optimisation problem in which there are a range of acceptable solutions with varying qualities, adapting the distributed service allocation is to the available deliberation time that is dynamically imposed as a result of emerging environmental conditions [9].…”
Section: Introductionmentioning
confidence: 99%
“…This is strictly related to the capacity of controlling the incoming workload, preventing abrupt and unpredictable degradations and achieving isolation among services, providing service guarantees to critical applications [1]. The Capacity Sharing and Stealing (CSS) scheduler [15] extends the resource reservation approach by proposing to handle overloads with additional capacity that is available from two sources: (i) by reclaiming unused allocated capacity when jobs complete in less than their budgeted execution time; and (ii) by stealing allocated capacities to non-isolated servers used to schedule sporadic besteffort jobs. The integration of the CSS scheduler into the CooperatES framework is discussed in detail in [12].…”
Section: The Cooperates Frameworkmentioning
confidence: 99%
“…The CooperatES (Cooperative Embedded Systems) framework [11,14,15] facilitates the cooperation among neighbours when a service request cannot be satisfyingly answered by a single node. Nodes dynamically group themselves into a new coalition, allocating resources to each new service and establishing an initial Service Level Agreement (SLA) that maximises the satisfaction of the QoS constraints associated with the new service and minimises the impact on the global QoS caused by the new service's arrival [11,14].…”
Section: Introductionmentioning
confidence: 99%
“…Based upon a careful study of the ways in which unused reserved capacities can be more efficiently used to meet deadlines of tasks whose resource usage exceeds their reservations, our previous work [16] proposed the coexistence of the traditional isolated servers with a novel non-isolated type of servers, combining an efficient reclamation of residual capacities with a controlled isolation loss. The goal of the Capacity Sharing and Stealing (CSS) scheduler is to reduce the mean tardiness of periodic guaranteed jobs by handling overloads with additional capacity available from two sources: (i) by reclaiming unused allocated capacity when jobs complete in less than their budgeted execution time; and (ii) by stealing allocated capacities from inactive non-isolated servers used to schedule aperiodic best-effort jobs.…”
Section: Introductionmentioning
confidence: 99%