Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Collect use cases for experiments #4

Open
lu-hub77 opened this issue Sep 7, 2021 · 0 comments
Open

Collect use cases for experiments #4

lu-hub77 opened this issue Sep 7, 2021 · 0 comments
Assignees

Comments

@lu-hub77
Copy link
Collaborator

lu-hub77 commented Sep 7, 2021

Possible use cases?

  • New product version (a new processor with improved characteristics) / product lines (powerful vs. affordable alternative) -> Exchange a processor
  • New product version with an additional functionality (more workload -> addition of tasks, communications)
  • Use of redundant processors -> In case of a failure of one processor (delete one processor) a bound task is rebound to a another processor (determined by the mapping options of a task); the communication structure is unaffected

Which aspects are not needed / not useful?

  • Not removing a large number of processors (each task still needs a valid mapping option to be able to find a valid implementation) -> a possible solution: Each task has at least two mapping options and only one processor is removed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants