Visitar URL original
Pod startup time phases are inaccurate in longer tests. · Issue #2006 · kubernetes/perf-tests · GitHub
Skip to content

Pod startup time phases are inaccurate in longer tests. #2006

Open

Description

@wojtek-t

gatherScheduleTimes:
https://github.com/kubernetes/perf-tests/blob/master/clusterloader2/pkg/measurement/common/slos/pod_startup_latency.go#L268
is currently listing events at the end of the test.

Given that events by default have 1h TTL, for measurements across longer periods it just returns incomplete results. Given that we don't 100% accuracy, we should switch to a mechanism that is similar to the one that slo-monitor is using (added in #1477 ).

Activity

  1. added
    help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
    good first issueDenotes an issue ready for a new contributor, according to the "help wanted" guidelines.
    on Mar 7, 2022
  2. sourikghosh commented on Mar 9, 2022

    @sourikghosh

    /assign

  3. k8s-triage-robot commented on Jun 7, 2022

    @k8s-triage-robot

    The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

    This bot triages issues and PRs according to the following rules:

    • After 90d of inactivity, lifecycle/stale is applied
    • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
    • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

    You can:

    • Mark this issue or PR as fresh with /remove-lifecycle stale
    • Mark this issue or PR as rotten with /lifecycle rotten
    • Close this issue or PR with /close
    • Offer to help out with Issue Triage

    Please send feedback to sig-contributor-experience at kubernetes/community.

    /lifecycle stale

  4. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Jun 7, 2022
  5. wojtek-t commented on Jun 9, 2022

    @wojtek-t
    MemberAuthor

    /remove-lifecycle stale

  6. removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Jun 9, 2022
  7. harshanarayana commented on Jun 18, 2022

    @harshanarayana

    @wojtek-t Is someone working on this still or can I take a stab at this ?

  8. harshanarayana commented on Jul 1, 2022

    @harshanarayana

    /assign

  9. k8s-triage-robot commented on Sep 29, 2022

    @k8s-triage-robot

    The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

    This bot triages issues and PRs according to the following rules:

    • After 90d of inactivity, lifecycle/stale is applied
    • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
    • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

    You can:

    • Mark this issue or PR as fresh with /remove-lifecycle stale
    • Mark this issue or PR as rotten with /lifecycle rotten
    • Close this issue or PR with /close
    • Offer to help out with Issue Triage

    Please send feedback to sig-contributor-experience at kubernetes/community.

    /lifecycle stale

  10. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Sep 29, 2022
  11. wojtek-t commented on Sep 29, 2022

    @wojtek-t
    MemberAuthor

    /remove-lifecycle stale

  12. removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Sep 29, 2022
  13. k8s-triage-robot commented on Feb 8, 2023

    @k8s-triage-robot

    The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

    This bot triages PRs according to the following rules:

    • After 90d of inactivity, lifecycle/stale is applied
    • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
    • After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

    You can:

    • Mark this PR as fresh with /remove-lifecycle stale
    • Close this PR with /close
    • Offer to help out with Issue Triage

    Please send feedback to sig-contributor-experience at kubernetes/community.

    /lifecycle stale

  14. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Feb 8, 2023
  15. wojtek-t commented on Feb 8, 2023

    @wojtek-t
    MemberAuthor

    /remove-lifecycle stale

  16. removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Feb 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

area/clusterloadergood first issueDenotes an issue ready for a new contributor, according to the "help wanted" guidelines.help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions