[
https://issues.apache.org/jira/browse/MESOS-970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15417455#comment-15417455
]
Guangya Liu commented on MESOS-970:
-----------------------------------
Actually, [~bmahler] already mentioned this in a JIRA here
https://issues.apache.org/jira/browse/MESOS-4558 and we do have plan to fix
this.
I think this was introduced by the review here
https://reviews.apache.org/r/49784/ as we are adding more test cases here for
allocator benchmark test.
{code}
INSTANTIATE_TEST_CASE_P(
SlaveAndFrameworkCount,
HierarchicalAllocator_BENCHMARK_Test,
::testing::Combine(
::testing::Values(1000U, 5000U, 10000U, 20000U, 30000U, 50000U),
::testing::Values(1U, 50U, 100U, 200U, 500U, 1000U, 3000U, 6000U))
);
{code}
There will be 48 (6 * 8) cases here and the longest benchmark test would have
50000 agents and 6000 frameworks as the test parameter, and also some test is
looping (framework * 2) times and for the last case, it would be 12000 loops,
that's why you see the benchmark test time is increasing.
We are now trying to find a solution for this so that we can also enable the
benchmark test in ASF CI. For now, perhaps you can use some filter to filter
out some test cases.
{code}
MESOS_BENCHMARK=1 GTEST_FILTER="*BENCHMARK*.*/1" make check
{code}
The above command will only run the first test case, you can adjust the
parameter based on your test requirement. Hope this helps.
> Upgrade bundled leveldb to 1.18
> -------------------------------
>
> Key: MESOS-970
> URL: https://issues.apache.org/jira/browse/MESOS-970
> Project: Mesos
> Issue Type: Improvement
> Components: replicated log
> Reporter: Benjamin Mahler
> Assignee: Tomasz Janiszewski
>
> We currently bundle leveldb 1.4, and the latest version is leveldb 1.18.
> Upgrade to 1.18 could solve the problems when build Mesos in some non-x86
> architecture CPU.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
