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.

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

Added a read rate limiter which allows limiting the read QpS per client #252

Merged
merged 1 commit into from
Jun 5, 2019

Conversation

kelindar
Copy link
Contributor

@kelindar kelindar commented Jun 5, 2019

This can be used in order to protect the broker from misbehaving clients. This PR also changes the previous writeRate to flushRate which is a more appropriate name.

	// The maximum messages per second allowed to be processed per client connection. This
	// effectively restricts the QpS for an individual connection.
	ReadRate int `json:"readRate,omitempty"`

	// The maximum socket write rate per connection. This does not limit QpS but instead
	// can be used to scale throughput. Defaults to 60.
	FlushRate int `json:"flushRate,omitempty"`

@kelindar kelindar merged commit b8c4d8e into master Jun 5, 2019
@delete-merged-branch delete-merged-branch bot deleted the feat-read-rate branch June 5, 2019 14:50
Florimond pushed a commit that referenced this pull request Sep 7, 2023
…nt (#252)

This can be used in order to protect the broker from misbehaving clients. This PR also changes the previous writeRate to flushRate which is a more appropriate name.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant