Reference : Squirrel: Architecture Driven Resource Management
Scientific congresses, symposiums and conference proceedings : Paper published in a book
Engineering, computing & technology : Computer science
Security, Reliability and Trust
http://hdl.handle.net/10993/26860
Squirrel: Architecture Driven Resource Management
English
Gonzalez-Herrera, Inti [University Of Rennes 1]
Bourcier, Johan [University of Rennes 1]
Rudametkin, Walter [University of Lille]
Barais, Olivier [University of Rennes 1]
Fouquet, François mailto [University of Luxembourg > Interdisciplinary Centre for Security, Reliability and Trust (SNT) > >]
2016
31st Annual ACM Symposium on Applied Computing (SAC'16)
Yes
No
International
31st Annual ACM Symposium on Applied Computing (SAC'16)
04-04-2016 to 08-04-2016
University of Pisa and Scuola Superiore Sant’Anna
Pisa
Italy
[en] Resource management is critical to guarantee Quality of Service when various stakeholders share the execution environment, such as cloud or mobile environments. In this context, providing management techniques compatible with standard practices, such as component models, is essential. Resource management is often realized through monitoring or pro- cess isolation (using virtual machines or system containers). These techniques (i) impose varying levels of overhead de- pending on the managed resource, and (ii) are applied at different abstraction levels, such as processes, threads or ob- jects. Thus, mapping components to system-level abstractions in the presence of resource management requirements can lead to sub-optimal systems. We propose Squirrel, an approach to tune component deployment and resource management in order to reduce management overhead. At run- time, Squirrel uses an architectural model annotated with resource requirements to guide the mapping of components to system abstractions, providing different resource management capabilities and overhead. We present an implementation of Squirrel, using a Java component framework, and a set of experiments to validate its feasibility and over- head. We show that choosing the right component-to-system mappings at deployment-time reduces performance penalty and/or volatile main memory use.
http://hdl.handle.net/10993/26860

File(s) associated to this reference

Fulltext file(s):

FileCommentaryVersionSizeAccess
Open access
typeinst.pdfPublisher postprint416.12 kBView/Open

Bookmark and Share SFX Query

All documents in ORBilu are protected by a user license.