Proceedings of the 2008 International Workshop on Software Engineering for Adaptive and Self-Managing Systems 2008
DOI: 10.1145/1370018.1370035
|View full text |Cite
|
Sign up to set email alerts
|

Scheduling time-bounded dynamic software adaptation

Abstract: Component-based software increasingly needs dynamic adaptation to support applications in domains such as automotive, avionics or robotic systems. Dynamic software adaptation involves both the integration of new, previously unanticipated features and the update of existing features without requiring system downtime. Software adaptations must often be time-bounded, e.g., due to mobility constraints. Inconsistent or inaccurate behaviour may result from an adaptation that does not complete within specified time c… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1

Citation Types

0
3
0

Year Published

2008
2008
2014
2014

Publication Types

Select...
3
1

Relationship

0
4

Authors

Journals

citations
Cited by 4 publications
(3 citation statements)
references
References 13 publications
0
3
0
Order By: Relevance
“…The entire dataset is available in our companion Web site. 10 We start by analyzing a Scale Out operation that deployed a new processing node to Cassandra. Figure 5 shows the evolution of the average CPU usage and CPU usage while performing disk I/O.…”
Section: Experiments Resultsmentioning
confidence: 99%
See 2 more Smart Citations
“…The entire dataset is available in our companion Web site. 10 We start by analyzing a Scale Out operation that deployed a new processing node to Cassandra. Figure 5 shows the evolution of the average CPU usage and CPU usage while performing disk I/O.…”
Section: Experiments Resultsmentioning
confidence: 99%
“…We can explain this behavior by recalling that Cassandra stops servicing requests when nodes are removed until it reorganizes the data. We associated the steady state after the drop to the end of the reconfiguration, 10 http://www.infosys.tuwien.ac.at/prototypes/elasticTesting/index.html therefore we considered the last change point that was detected as end of the reconfiguration. The average CPU usage had only a little increase after the reconfiguration because in the default settings Cassandra randomly distributed the load across processing nodes, and in this experiment the processing node that was removed was lightly loaded.…”
Section: Experiments Resultsmentioning
confidence: 99%
See 1 more Smart Citation