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

Functionbeat use a concurrency of 5 by default for AWS lambda #8992

Merged
merged 2 commits into from
Nov 15, 2018

Conversation

ph
Copy link
Contributor

@ph ph commented Nov 8, 2018

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.

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.
@ph ph added in progress Pull request is currently in progress. Functionbeat labels Nov 8, 2018
@ph
Copy link
Contributor Author

ph commented Nov 8, 2018

Lets get that merged after 6.5.0 this is why I've marked it as a in progress.

@ph ph changed the title [WIP] Use a concurrency of 5 by default [WIP] Functionbet use a concurrency of 5 by default for AWS lambda Nov 8, 2018
@ph ph changed the title [WIP] Functionbet use a concurrency of 5 by default for AWS lambda [WIP] Functionbeat use a concurrency of 5 by default for AWS lambda Nov 8, 2018
@ph
Copy link
Contributor Author

ph commented Nov 9, 2018

jenkins test this please

@ph ph changed the title [WIP] Functionbeat use a concurrency of 5 by default for AWS lambda Functionbeat use a concurrency of 5 by default for AWS lambda Nov 9, 2018
@ph ph added review and removed in progress Pull request is currently in progress. labels Nov 9, 2018
}

type lambdaConfig struct {
Concurrency int `config:"concurrency" validate:"positive"`
Concurrency int `config:"concurrency" validate:"min=0,max=1000"`
Copy link
Contributor

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?

Copy link
Contributor Author

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.

Copy link
Contributor

@exekias exekias left a 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

@exekias
Copy link
Contributor

exekias commented Nov 12, 2018

Will need a changelog if merged after cut

@ph
Copy link
Contributor Author

ph commented Nov 12, 2018

@exekias I have added a changelog, we don't want it for 6.5.0.

@ph ph merged commit e2d9287 into elastic:master Nov 15, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants