[go: nahoru, domu]
Skip to content
This repository has been archived by the owner on Jun 19, 2022. It is now read-only.

Determine default target for broker ingress events per second #1596

Closed
grantr opened this issue Aug 18, 2020 · 2 comments
Closed

Determine default target for broker ingress events per second #1596

grantr opened this issue Aug 18, 2020 · 2 comments
Assignees
@yolocs
Labels
area/broker kind/feature-request New feature or request priority/1 Blocks current release defined by release/* label or blocks current milestone release/2 storypoint/2
Projects
GCP Broker
Milestone
v0.18.0-M1

Comments

@grantr
Copy link
Contributor
grantr commented Aug 18, 2020 •
edited
Loading

Problem
What is our default target for published events per second handled by the broker ingress service? This is separate from the fanout's delivered events per second (and is likely to be lower).

Persona:
User

Exit Criteria
We have a goal in published events per second to tune the default ingress resource requirements.

Part of #1552.
@grantr grantr added release/2 priority/1 Blocks current release defined by release/* label or blocks current milestone kind/feature-request New feature or request area/broker labels Aug 18, 2020
@grantr grantr added this to Backlog in GCP Broker via automation Aug 18, 2020
This was referenced Aug 18, 2020
Closed
Closed
@grantr
Copy link
Contributor Author
grantr commented Aug 18, 2020

@liu-cong suggests default target 1000 events per second.

@grantr grantr added this to the v0.18.0-M1 milestone Aug 19, 2020
@yolocs
Copy link
Member
yolocs commented Aug 24, 2020

The default target I'm setting for a single ingress pod is: <= 1000 qps, <= 256k event size.

@grantr grantr moved this from Backlog to In progress in GCP Broker Aug 25, 2020
@grantr grantr moved this from In progress to Prioritized Backlog in GCP Broker Aug 25, 2020
@grantr grantr closed this as completed Sep 2, 2020
GCP Broker automation moved this from Prioritized Backlog to Done Sep 2, 2020
@yolocs yolocs mentioned this issue Sep 14, 2020
Closed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@yolocs yolocs

Labels
area/broker kind/feature-request New feature or request priority/1 Blocks current release defined by release/* label or blocks current milestone release/2 storypoint/2
Projects
GCP Broker
  
Done
Milestone
v0.18.0-M1
Development

No branches or pull requests
2 participants
@grantr @yolocs