Re:Show HN: Meadowrun automates the tedious details of runni...
by hrichardlee1 on Friday June 10, 2022 @11:33AM
(#31695588)
Yes! (in some cases) The tradeoffs are that lambdas are way faster to start up, but they max out at 10GB of memory, 15 minutes of runtime, you can't use GPUs, and you get 250MB to store your code (you get more if you build a container) and 512MB of temp space. We're in the middle of working on adding this as an option--we want to make it seamless to switch between running your code on Lambda (for short, quick jobs) vs EC2 (for longer, more resource-intensive jobs) depending on what kind of workload you have.
[ Parent
| on HN ]
Re:Show HN: Meadowrun automates the tedious details of runni...
by r00tanon on Friday June 10, 2022 @02:36PM
(#31697819)
Good news. We've found lambdas orchestrated with step functions and properly split out as to function can do a lot of data processing even with the limits you stated before needing to switch over to AWS batch or ECS. Nice to have that tool in the belt. I'll check it out.
Re:Show HN: Meadowrun automates the tedious details of runni...
by by_the_bay on Friday June 10, 2022 @12:11PM
(#31696111)
Cool, look forward to trying it out