Difference between revisions of "Resilience Research Questions"

From Modelado Foundation Wiki
Jump to: navigation, search

Deprecated: The each() function is deprecated. This message will be suppressed on further calls in /var/www/modelado-wiki/includes/diff/DairikiDiff.php on line 434
(Created page with "Below are the questions addressed in the Resiliance Research Panel. Please add your comments (with you name) after each question. == Challenges == What resilience challenges f...")
 
(Added questions for 2014 resilience panel)
Line 1: Line 1:
Below are the questions addressed in the Resiliance Research Panel. Please add your comments (with you name) after each question.
+
Below are the questions addressed in the Resilience Research Panel. Please add your comments (with you name) after each question.
== Challenges ==
+
 
What resilience challenges for exascale systems are you aiming to address?  (and any open challenges)
+
1) What features of other levels of the stack (algorithm, programming model, compiler, runtime, and hardware) should resilience depend on?
== Results and Capabilities ==
+
 
What recent results and capabilities can you share?
+
 
== Technologies ==
+
2) How can resilience schemes best exploit application, runtime, or programming model semantics?
How will new resilience technologies capabilities be demonstrated?
+
 
== Convergence ==
+
 
How will new resilience technologies come together with other resilience technologies?  Other X-stack technologies?
+
3) What are the biggest missing pieces needed from the various layers to make resilience schemes succeed?
 +
 
 +
 
 +
4) What is the impact on resilience of the wide range of expected operating scenarios with respect to dynamically changing resources, application characteristics, and the wide range of possible error and failure rates?

Revision as of 03:27, 16 May 2014

Below are the questions addressed in the Resilience Research Panel. Please add your comments (with you name) after each question.

1) What features of other levels of the stack (algorithm, programming model, compiler, runtime, and hardware) should resilience depend on?


2) How can resilience schemes best exploit application, runtime, or programming model semantics?


3) What are the biggest missing pieces needed from the various layers to make resilience schemes succeed?


4) What is the impact on resilience of the wide range of expected operating scenarios with respect to dynamically changing resources, application characteristics, and the wide range of possible error and failure rates?