[
https://issues.apache.org/jira/browse/YUNIKORN-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17730959#comment-17730959
]
Peter Bacsko commented on YUNIKORN-1786:
----------------------------------------
{quote}Peter Bacsko would this tool help and or can it be used with KWOK also?
{quote}
Yes, if this is a test which can drive both the default scheduler and Yunikorn
then it is useful for us because it allows direct comparison between the two
(performance-wise).
Talked to Wei Huang (Kwok dev), on a sufficiently powerful machine, Kwok can
simulate more than 1k nodes (quoting him verbatim):
_"above 1k is fine, like I usually use my m1 laptop to test 2k or even 5k
nodes. Given the internal design of kwok, memory should not be a problem. The
problem may lie in the cpu consumption of control plane components, this is in
particular important if you run the control plane in a containerized env"_
> perf-tools build and dependency updates
> ---------------------------------------
>
> Key: YUNIKORN-1786
> URL: https://issues.apache.org/jira/browse/YUNIKORN-1786
> Project: Apache YuniKorn
> Issue Type: Task
> Components: release
> Reporter: Wilfred Spiegelenburg
> Priority: Major
>
> Multiple old dependencies in the perf-tools that should be updated:
> * references a really old core which does not have the changes in which we
> moved all memory resources to bytes.
> * K8s version is stuck at 1.20 (should move to at least 1.23)
> * gotest.tools is on v2 all other code is on v3
> * gopkg.in/yaml.v2 is running behind
> Release repo should also use go version file to enforce building with a
> recent go version as the other repos do.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
