-
Notifications
You must be signed in to change notification settings - Fork 37
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
feat/Policer enhancements #2600
Changes from all commits
21c3328
060244f
32cecb9
6a69293
388dac2
40762d3
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -94,6 +94,11 @@ apiclient: | |
|
||
policer: | ||
head_timeout: 15s # timeout for the Policer HEAD remote operation | ||
cache_size: 1000001 # recently-handled objects cache size | ||
cache_time: 31s # recently-handled objects cache expiration time | ||
replication_cooldown: 101ms # cooldown time b/w replication tasks submitting | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. it's implemented like interval, not cooldown, so why is it called so? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
what do you mean here? the current implementation is what i would call a cooldown (but i could be wrong) There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. if There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. lets use some ascii paintings here Rs -- replication started
a cooldown to me is "i used some func, next time i will be able to use it no earlier than after *cooldown_time*" |
||
object_batch_size: 11 # replication's objects batch size | ||
max_workers: 21 # replication's worker pool's maximum size | ||
|
||
replicator: | ||
put_timeout: 15s # timeout for the Replicator PUT remote operation (defaults to 1m) | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
size
andtime
tocache
section?but 1st of all: why do we expose all parameters while #2590 suggests
replication_cooldown
only?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
well, could be done but i am almost sure the resulting config will change so lets wait testing results and see what we need
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the whole PR is a suggestion. we have magic consts and I am not sure how they work. so now we have a PR that can be tested