Skip to content

Nonfunctional Baseline Testing #616

Closed
@mpstefan

Description

@mpstefan

The objective of baseline establishment is to understand how changes to the system either improve or negatively impact performance of the system.

In the case of NGINX this relates to both the establishment of sane defaults that help customers have immediate success as well as the impacts of configuration changes (how long they take, how efficient are we at reducing reloading impacts, etc.)

The objective is not measuring the performance of NGINX itself, it is measuring the impacts of the NKG controller system.

Discussion: #752

### Tasks
- [ ] https://github.com/nginxinc/nginx-kubernetes-gateway/issues/950
- [ ] https://github.com/nginxinc/nginx-kubernetes-gateway/issues/951
- [ ] https://github.com/nginxinc/nginx-kubernetes-gateway/issues/952
- [ ] https://github.com/nginxinc/nginx-kubernetes-gateway/issues/953
- [ ] https://github.com/nginxinc/nginx-kubernetes-gateway/issues/954
- [ ] https://github.com/nginxinc/nginx-kubernetes-gateway/issues/955
- [ ] https://github.com/nginxinc/nginx-kubernetes-gateway/issues/956

Questions for Discussion

  • Do we absolutely need all of the baseline tests above?
  • Do we have an idea of how long each would take?
  • Where can we track the results?

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestepicRepresents an epic. Contains sub-issuesrefinedRequirements are refined and the issue is ready to be implemented.

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions