fix(perf): increase MAX_AGE_MINUTES to 120 (#215)
- When experimenting with increasing iterations, instances are taken down prematurely. See e.g. https://github.com/libp2p/test-plans/actions/runs/5418669631/jobs/9850992882 - When benchmarking from a local developer machine, experimenting for longer is useful. - The AWS Lambda is only a safety net machanism. In the rare case where we miss to clean up, running the machines for <1h or 2h doesn't matter cost wise.
This commit is contained in:
parent
1b187a379c
commit
acea8b5e0c
|
@ -18,7 +18,7 @@ resource "aws_lambda_function" "cleanup" {
|
|||
variables = {
|
||||
REGIONS = jsonencode(var.regions)
|
||||
TAGS = jsonencode(var.tags)
|
||||
MAX_AGE_MINUTES = 50
|
||||
MAX_AGE_MINUTES = 120
|
||||
}
|
||||
}
|
||||
}
|
||||
|
|
|
@ -13,7 +13,7 @@ Resources:
|
|||
Variables:
|
||||
REGIONS: '["us-west-2", "us-east-1"]'
|
||||
TAGS: '{"Project":"perf", "Name":"node"}'
|
||||
MAX_AGE_MINUTES: '30'
|
||||
MAX_AGE_MINUTES: '120'
|
||||
Policies:
|
||||
- AmazonEC2FullAccess
|
||||
Timeout: 30
|
||||
|
|
Loading…
Reference in New Issue