-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Add benchmarks for critical components and hot paths. #6749
Copy link
Copy link
Closed
Labels
area/autoscalegood first issueDenotes an issue ready for a new contributor, according to the "help wanted" guidelines.Denotes 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.Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.Denotes an issue or PR has remained open with no activity and has become stale.
Metadata
Metadata
Assignees
Labels
area/autoscalegood first issueDenotes an issue ready for a new contributor, according to the "help wanted" guidelines.Denotes 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.Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.Denotes an issue or PR has remained open with no activity and has become stale.
Knative intends to add as little overhead to pure HTTP as possible. As such, some of our components are exposed to the hot-path of just about each HTTP request coming into and flowing through the system.
We need benchmarks (both micro and macro) to be able to reason about the impact of changes we do and to be able to quickly iterate on different strategies to remove that overhead.
Off the top of my mind, we need benchmarks for:
Each of these can be taken individually, an example for handler benchmarks is
serving/pkg/activator/handler/handler_test.go
Lines 435 to 500 in f65d5a7
serving/pkg/http/request_log_test.go
Lines 241 to 263 in f65d5a7