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

End-to-End Quality of Service Management for Distributed Real-Time Embedded Applications

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
10
0

Publication Types

Select...
3
2
2

Relationship

0
7

Authors

Journals

citations
Cited by 17 publications
(10 citation statements)
references
References 10 publications
0
10
0
Order By: Relevance
“…RELATED WORK Compared to related research presented in [19], the resource management framework used in MACRO -RACE -is an adaptive resource management framework that can be customized and configured using model-driven deployment and configuration tools such as the Platform-Independent Component Modeling Language (PICML) [20]. Moreover, RACE provides adaptive resource and QoS management capabilities more transparently and non-intrusively than Kokyu [21], QuO [22], and Qoskets [23], [24], [25]. In particular, it allocates CPU, memory, and networking resources to application components and tracks and manages utilization of various system resources, as well as application QoS.…”
Section: ) Summarymentioning
confidence: 99%
“…RELATED WORK Compared to related research presented in [19], the resource management framework used in MACRO -RACE -is an adaptive resource management framework that can be customized and configured using model-driven deployment and configuration tools such as the Platform-Independent Component Modeling Language (PICML) [20]. Moreover, RACE provides adaptive resource and QoS management capabilities more transparently and non-intrusively than Kokyu [21], QuO [22], and Qoskets [23], [24], [25]. In particular, it allocates CPU, memory, and networking resources to application components and tracks and manages utilization of various system resources, as well as application QoS.…”
Section: ) Summarymentioning
confidence: 99%
“…The design of the LRM is illustrated in Figure 9 and described in more detail in [15]. The LRM takes as inputs the resource allocations, minimums and maximums for each QoS attribute (e.g., size, rate, compression level, etc.…”
Section: The Prototype Local Resource Managermentioning
confidence: 99%
“…The others will be starved (i.e., receive no resource allocation). This metric looks for the feasible solution that runs the highest number of applications (whether that solution is the highest utility solution or not 15 ) and collect the number of applications running as a percentage of the number available to run. C. Highest percent of applications requesting the most-shared resource: In general, as more applications request a given resource, the contention for the resource increases.…”
Section: B Highest Percent Of Applications Not-starved In Any Feasibmentioning
confidence: 99%
See 1 more Smart Citation
“…Our QoS management capability extends existing IMS middleware to manage the production, delivery, and consumption of information that meets client needs within available resources, to mediate competing demands for resources, and to adjust to dynamic conditions. Our QoS Management System (QMS) middleware, illustrated in Figure 1, builds upon our previous work in QoS management for distributed object and component systems [7,15,16,17,18,19,28]. The QMS is multi-layered middleware, described in more detail in [14], with an information space QoS manager (ISQM) 1 that provides aggregate QoS allocations and policy for clients and operations throughout an information space.…”
Section: Introductionmentioning
confidence: 99%