Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Performance Acceptance Testing - Verification #166

Open
tpoland opened this issue Mar 3, 2021 · 1 comment
Open

Performance Acceptance Testing - Verification #166

tpoland opened this issue Mar 3, 2021 · 1 comment
Labels
TYPE: Performance

Comments

@tpoland
Copy link
Contributor

tpoland commented Mar 3, 2021

A concern was raised about potential performance regressions when migrating from 1.10.x to 2.0.x potentially requiring more resources (routers, traffic controllers, dopplers, and AIs) to maintain the original level of performance for that application. We'd like to use the upstream performance acceptance tests to compare performance between our 1.10.4 and 2.0.3 kits as confirmation that performance remains consistent or improves.
@tpoland tpoland mentioned this issue Mar 3, 2021
Open
@mrferris mrferris reopened this Aug 2, 2021
@mrferris
Copy link
Contributor

mrferris commented Aug 2, 2021

Performance testing is still a requirement we haven't fulfilled (as far as I know)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
TYPE: Performance
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@tpoland @ramonskie @mrferris