[
https://issues.apache.org/jira/browse/MESOS-4429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niklas Quarfot Nielsen updated MESOS-4429:
------------------------------------------
Description:
To evaluate the function and quality of oversubscription modules, we could ship
a test framework which can:
1) Launch on oversubscribed and non-oversubscribed resources in a controlled
manner. For example, register as two different frameworks and see that
resources from slack resources of one framework can be used by the other.
2) Measure time to react for different scenarios. For example, measure the time
it takes from slack appearing on a slave to the offer being issued with
revocable resources. The time to react for changing usage patterns e.g. time to
reclaim oversubscribed resources when regular tasks need them back.
3) Count the number of offer rescind, preemptions, etc. to deem the stability
of the policy.
4) Be able to measure % extra work being able to run.
5) Work across different resource dimensions as cpu time, memory, network,
caches.
[~Bartek Plotka] has been working on something similar for Serenity in
https://github.com/mesosphere/serenity/tree/master/src/framework which we can
reuse as a base.
was:
To evaluate the function and quality of oversubscription modules, we could ship
a test framework which can:
1) Launch on oversubscribed and non-oversubscribed resources in a controlled
manner. For example, register as two different frameworks and see that
resources from slack resources of one framework can be used by the other.
2) Measure time to react for different scenarios. For example, measure the time
it takes from slack appearing on a slave to the offer being issued with
revocable resources. The time to react for changing usage patterns e.g. time to
reclaim oversubscribed resources when regular tasks need them back.
3) Count the number of offer rescind, preemptions, etc. to deem the stability
of the policy.
4) Be able to measure % extra work being able to run.
5) Work across different resource dimensions as cpu time, memory, network,
caches.
[~Bartek Plotka] has been working on something similar for Serenity in
https://github.com/mesosphere/serenity/tree/master/src/framework which we can
reuse as a base.
> Add oversubscription benchmark/stress/test framework
> ----------------------------------------------------
>
> Key: MESOS-4429
> URL: https://issues.apache.org/jira/browse/MESOS-4429
> Project: Mesos
> Issue Type: Task
> Reporter: Niklas Quarfot Nielsen
>
> To evaluate the function and quality of oversubscription modules, we could
> ship a test framework which can:
> 1) Launch on oversubscribed and non-oversubscribed resources in a controlled
> manner. For example, register as two different frameworks and see that
> resources from slack resources of one framework can be used by the other.
> 2) Measure time to react for different scenarios. For example, measure the
> time it takes from slack appearing on a slave to the offer being issued with
> revocable resources. The time to react for changing usage patterns e.g. time
> to reclaim oversubscribed resources when regular tasks need them back.
> 3) Count the number of offer rescind, preemptions, etc. to deem the stability
> of the policy.
> 4) Be able to measure % extra work being able to run.
> 5) Work across different resource dimensions as cpu time, memory, network,
> caches.
> [~Bartek Plotka] has been working on something similar for Serenity in
> https://github.com/mesosphere/serenity/tree/master/src/framework which we can
> reuse as a base.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
