-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Functionbeat use a concurrency of 5 by default for AWS lambda #8992
Functionbeat use a concurrency of 5 by default for AWS lambda #8992
Conversation
This change the previous default of an unreserved concurrency, this allow to have a more sane value to keep the cost down and still allow people to turn the knob up to get better performance.
Lets get that merged after 6.5.0 |
jenkins test this please |
} | ||
|
||
type lambdaConfig struct { | ||
Concurrency int `config:"concurrency" validate:"positive"` | ||
Concurrency int `config:"concurrency" validate:"min=0,max=1000"` |
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.
I'm wondering, is 1000 as hard maximum in AWS?
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.
It is indeed a weird setting, it is a hard limit per account of the total of running function of any kind.
IE: if you set this function to 5, It will run a maximum of 5 of your function.
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.
LGTM, left a question
Will need a changelog if merged after cut |
@exekias I have added a changelog, we don't want it for 6.5.0. |
This change the previous default of an unreserved concurrency, this
allow to have a more sane value to keep the cost down and still
allow people to turn the knob up to get better performance.