3 ms·
Lambda is never meant for low latency CPU app, where speed is king, due to startup cost. I don’t see why you would run architecture specific code on lambda.
by aynyc 5y ago
Lambda is never meant for low latency CPU app, where speed is king, due to startup cost. I don’t see why you would run architecture specific code on lambda.
- estebarb 5y agoThere are languages like Go, Rust or C that are compiled. If your lambda uses compiled languages you need to recompile to the right platform. Additionally, a lot of interpreted languages depends on native libraries. You need to build those libraries using the right arch. It happens a lot if you want, for example, deploy a Rails app in Lambda. By the way, Lambda works great for low latency apps. The "startup cost" is negligible if you know how to implement it. You can serve ML models from a lambda, and in that case you want a math library optimized for the platform. Unless you have a lot of traffic a Lambda usually is cheaper.
- Rebelgecko 5y agoThere are plenty of usecases where latency isn't that important but speed is (e.g. reencoding an hour long video file)
- tehbeard 5y agoI wouldn't have a task that would quite so extensive on lambda (though tbh I don't know how it costs compared to aws' video encoder service) But in a similar vein, extracting interesting thumbnails would at scale, be one use case where lambda with assembly/compiled static bins may be a good choice.