Re:New for AWS Lambda – Environment Variables and Serverless...
by Jdam on Sunday November 20, 2016 @01:35PM
(#13000300)
Don't use it if you require low latency - performance is abysmal and the bottleneck is Lambda overhead that you cannot influence.
Also, if you don't have a high traffic function, cold start is also an issue, at least when using Java. There is a "hack" to avoid this issue: create a cloudwatch check that triggers your function every minute or so. This sounds weird but if you consider that this is good practice, this gives you an overview how production-ready Lambda is. Nice thing is that is's pretty cheap though.
[ Parent
| on HN ]
Re:New for AWS Lambda – Environment Variables and Serverless...
by tedmiston on Sunday November 20, 2016 @03:13PM
(#13000906)
Warming it every minute seems kind of excessive. Did you really have to do it that much? I haven't experienced this with Python but my jobs are more cron-ish so an extra 100 ms doesn't make a difference.
Re:New for AWS Lambda – Environment Variables and Serverless...
by brianwawok on Sunday November 20, 2016 @03:31PM
(#13001001)
Loading JVM from a cold VM is a lot more than 100ms, more like 5-10 seconds. Same problem Google App Engine had 7 years ago before you could pay to keep an instance warm.