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

Tests Product Telemetry Performance #1561

Closed
ja20222 opened this issue Feb 12, 2024 · 1 comment
Closed

Tests Product Telemetry Performance #1561

ja20222 opened this issue Feb 12, 2024 · 1 comment
Assignees
@pleshakov
Labels
area/telemetry Issues related to collected telemetry data refined Requirements are refined and the issue is ready to be implemented. size/small Estimated to be completed within ~2 days tests Pull requests that update tests
Milestone
v1.2.0

Comments

@ja20222
Copy link

ja20222 commented Feb 12, 2024 •
edited
Loading

As a maintainer of the NGF project,
I want to verify the performance of product telemetry logic,
So that I can ensure no unnecessary overhead

Acceptance Criteria

  • We may want to run two simultaneous longevity tests to compare CPU and Memory overhead with telemetry on and with telemetry off.

Dev note
Increase the reporting frequency for the tests (Every Hour)
@ja20222 ja20222 added tests Pull requests that update tests area/telemetry Issues related to collected telemetry data labels Feb 12, 2024
@sjberman sjberman mentioned this issue Feb 12, 2024
Closed
@sjberman sjberman added this to the v1.2.0 milestone Feb 12, 2024
@ja20222 ja20222 added refined Requirements are refined and the issue is ready to be implemented. size/small Estimated to be completed within ~2 days labels Feb 12, 2024
@pleshakov pleshakov added the blocked Blocked by other issue label Feb 26, 2024
@pleshakov
Copy link
Contributor

blocked by #1377

@pleshakov pleshakov removed the blocked Blocked by other issue label Mar 7, 2024
@pleshakov pleshakov self-assigned this Mar 11, 2024
pleshakov added a commit to pleshakov/nginx-gateway-fabric that referenced this issue Mar 19, 2024
@pleshakov
Added product telemetry performance test results
088262a 
Problem:
Ensure the product telemetry feature doesn't negatively affect
NGINX Gateway Fabric performance: CPU and memory usage.

Solution:
- Test performance.
- Share results.

CLOSES - nginx#1561
pleshakov added a commit to pleshakov/nginx-gateway-fabric that referenced this issue Mar 19, 2024
@pleshakov
Added product telemetry performance test results
e69aae2 
Problem:
Ensure the product telemetry feature doesn't negatively affect
NGINX Gateway Fabric performance: CPU and memory usage.

Solution:
- Test performance.
- Share results.

CLOSES - nginx#1561
@pleshakov pleshakov mentioned this issue Mar 19, 2024
Merged
6 tasks
pleshakov added a commit that referenced this issue Mar 19, 2024
@pleshakov
Added product telemetry performance test results (#1727)
e1ef3d1 
* Added product telemetry performance test results

Problem:
Ensure the product telemetry feature doesn't negatively affect
NGINX Gateway Fabric performance: CPU and memory usage.

Solution:
- Test performance.
- Share results.

CLOSES - #1561
amimimor pushed a commit to amimimor/nginx-gateway-fabric that referenced this issue Apr 3, 2024
@pleshakov @amimimor
Added product telemetry performance test results (nginx#1727)
71d0f1a 
* Added product telemetry performance test results

Problem:
Ensure the product telemetry feature doesn't negatively affect
NGINX Gateway Fabric performance: CPU and memory usage.

Solution:
- Test performance.
- Share results.

CLOSES - nginx#1561
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pleshakov pleshakov

Labels
area/telemetry Issues related to collected telemetry data refined Requirements are refined and the issue is ready to be implemented. size/small Estimated to be completed within ~2 days tests Pull requests that update tests
Projects
None yet
Milestone
v1.2.0
Development

No branches or pull requests
3 participants
@pleshakov @sjberman @ja20222