[
https://issues.apache.org/jira/browse/MESOS-4558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15374768#comment-15374768
]
Guangya Liu commented on MESOS-4558:
------------------------------------
Selectively run benchmark test is also an option, but not sure if there are any
logic for how to select the representative benchmark test.
Take this patch https://reviews.apache.org/r/49784/ as an example, after it was
merged, it will introduce some cases that agent count is less than framework
count, which may lead some frameworks cannot get resources and the allocator
will try to allocate resources on fully used agents. This is a good test cases
to check if the fully used agent resources can impact the performance of the
allocator. But the problem is how we can select the cases which can cover the
cases of fully used agent with some filters?
Also in https://reviews.apache.org/r/49784/ , we enabled {{batchsize}} to do
less loop for frameworks, this seems a simple way to decrease the time of the
benchmark test without updating the filter logic of ASF CI.
> Reduce the running time of benchmark tests.
> -------------------------------------------
>
> Key: MESOS-4558
> URL: https://issues.apache.org/jira/browse/MESOS-4558
> Project: Mesos
> Issue Type: Task
> Reporter: Vinod Kone
> Labels: newbie++
>
> Currently benchmark tests take a long time (>5 hours). It would be nice to
> reduce the total time taken by the benchmark tests to enable us to run them
> on ASF CI.
> Command to run only benchmark tests
> {code}
> MESOS_BENCHMARK=1 GTEST_FILTER="*BENCHMARK*" make check
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
