Skip to content

device-monitoring: lambda memory size increase #189

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 2 commits into from
Feb 14, 2024
Merged

device-monitoring: lambda memory size increase #189

merged 2 commits into from
Feb 14, 2024

Conversation

@aaronatbissell
Copy link
Contributor

@aaronatbissell aaronatbissell commented Feb 8, 2024

Description

The device monitoring lambda regularly uses ~300MB per lambda invocation. 128MB will not even run, the lambdas are timing out.

Screenshot 2024-02-08 at 3 53 29 PM

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Refactor (existing code being refactored)
  • This change includes a documentation update

Submission Checklist

  • CI dry-run passing
  • Integration tests passing locally
  • Change logs generated
Additional Notes:

@ts-amz ts-amz merged commit e62ce70 into aws:main Feb 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@ts-amz ts-amz ts-amz approved these changes

+1 more reviewer

@nrusson nrusson nrusson approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@aaronatbissell @nrusson @ts-amz