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

Custom memory_size for async tasks #1326

Closed
th0th opened this issue Jan 2, 2018 · 2 comments
Closed

Custom memory_size for async tasks #1326

th0th opened this issue Jan 2, 2018 · 2 comments

Comments

@th0th
Copy link

th0th commented Jan 2, 2018

tl;dr

Is it possible to set a different memory size (different than memory_size set in zappa_settings.json) for async tasks? If not, is it on the roadmap? I am not sure if AWS Lambda offers such functionality.

A little bit detail

I have custom async tasks that does some heavy tasks asynchronously. If I set the global memory_size accordingly, I am wasting a certain amount of that memory. If I set a low memory_size, then my asynchronous tasks are going to fail.

As I described in the short description of the issue, I am not sure if there is an AWS Lambda limitation, but I it would be lovely to be able to set memory_size as a parameter like @task(memory_size=512) in zappa.async.task decorator or in zappa.async.run.

@jwkvam
Copy link
Contributor

jwkvam commented Jan 5, 2018

I think there's a constraint of 1 Lambda Function to 1 Zappa app. If that's true, you'd need to setup another Lambda function and use boto to invoke it.

Edit: Nevermind, I think you simply need to make another Lambda function.

@th0th
Copy link
Author

th0th commented Jan 6, 2018

@jwkvam Thanks for the explanation.

@th0th th0th closed this as completed Jan 6, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants