This is still scam. no matter what it costs.
AWS Lambda pricing now per ms
151–160 of 291 posts
Re: AWS Lambda pricing now per ms
#152Earlier quoted context omitted.
Just out of curiosity, what are you getting out of your 160 million CPU cycles? Are you mostly on the CPU, or mostly waiting for something (database call or whatever)?
I want to do something that a low level hacker could do in 100 clock cycles with hardcoded bit twiddling and some avx-512, but I want to use nodejs, so I'm gonna need at least 100 million clock cycles to parse all the npm modules...
Not sure why you need a whole bunch of npm modules to do bit twiddling in a performance-sensitive lambda function. Sounds like you just don't like Javascript.
Edit: You're spending like 80ms on cold-start of your lambda function, plus network overhead. If you can spare that, you can likely spare the half a millisecond for the 999,900 cycles you're complaining about.
Re: AWS Lambda pricing now per ms
#15366$ for running a AWS Lambda with 128 for a year seems very expensive.
And it costs even more if you need that Lambda function to have access to the internet. A possibly useful comparison: A Raspberry Pi 3 (~6.5 watts) costs $6.83 per year to run full-time (at 12 cents per kWh). You get a full computer with much more I/O. However, there are a lot of other factors to consider: - Initial cost of the hardware - Time and energy spent maintaining/configuring the device - Physical maintenance…
A RPi 3 has an upfront cost of over 10 dollars. With lambda you can start with pennies.
Re: AWS Lambda pricing now per ms
#154I am curious to see if this will mean a shift to more efficient languages (Go or Rust) for Lambda services, as usually people default to JS
From the research I did, here's how languages stack up in Lambda runtime (lowest first): 1. Python & JS 2. Go 3. C# & Java I couldn't find any data on Rust. The understanding at the time was that Python & JS runtimes are built-in, so the interpreter is "already running" Go is the fastest of compiled languages, but just can't beat the built-in runtimes. C# and Java were poorest as they're spinning up a larger runtime…
The numbers you link don’t support your ranking, unless you’re specifically ranking by cold start alone.
Even then it doesn’t make sense to group Python and Node but not Go, as Node and Go are significantly closer than Node to Python.
Re: AWS Lambda pricing now per ms
#155Earlier quoted context omitted.
Awesome! That was the idea here. Lots of sub 100ms workloads and we really want you to be able to pay for what you use. - Chris, Serverless@AWS
Wait, are you Chris Munns from Music2Go? If so, massively small world. My email is username @setec.io; would love to hear from you. -Harlan, the ex-intern
It me.
Re: AWS Lambda pricing now per ms
#156Is there a way to use lambda where I can use ffmpeg to watermark and downscale a 4K video? Possibly some system where I can throw a lot of computing at the job and get it done quickly. Right now on my vps it takes multiple minutes to get done and scaling up the vps for one feature or dedicating another server for it is overkill.
Re: AWS Lambda pricing now per ms
#157Is there a way to use lambda where I can use ffmpeg to watermark and downscale a 4K video? Possibly some system where I can throw a lot of computing at the job and get it done quickly. Right now on my vps it takes multiple minutes to get done and scaling up the vps for one feature or dedicating another server for it is overkill.
Another subission today seems to point to exactly what you're looking for - https://aws.amazon.com/blogs/aws/new-for-aws-lambda-function...
Re: AWS Lambda pricing now per ms
#158Is there a way to use lambda where I can use ffmpeg to watermark and downscale a 4K video? Possibly some system where I can throw a lot of computing at the job and get it done quickly. Right now on my vps it takes multiple minutes to get done and scaling up the vps for one feature or dedicating another server for it is overkill.
This works well: https://github.com/serverlesspub/ffmpeg-aws-lambda-layer
Re: AWS Lambda pricing now per ms
#159Necessary change. Now writing stuff in fast languages suddenly matter in cost, changing the landscape of when these solutions might become viable for a chase.
And you can pick any language you'd like as it supports arbitrary containers now too: https://news.ycombinator.com/item?id=25267182
Oh that's quite big news if you run an app that has to be deployed cross cloud.
We use very little serverless at the moment, because the three clouds we need to deploy to have infuriating differences between their execution and deployment environments. Eg. How they manage dependancies, the runtimes, how you describe and deploy each function.
Compared at least to K8 where the containers you build run just fine wherever you put them.
Re: AWS Lambda pricing now per ms
#160Is there a way to use lambda where I can use ffmpeg to watermark and downscale a 4K video? Possibly some system where I can throw a lot of computing at the job and get it done quickly. Right now on my vps it takes multiple minutes to get done and scaling up the vps for one feature or dedicating another server for it is overkill.
I don't see why not, assuming it's less than the lambda max run time (15 minutes I believe). Use a python script and an included binary of ffmpeg might work. Note: You'll need to write to the tmp space of the lambda as that's the only place that allows writing to the filesystem and then you'll need to upload it to S3 or elsewhere.
Lambda's are good at batch jobs where you might need to kick off a few of them but not have a dedicated system for it. I've used it to automate manual customer support tasks that are sporadic in requests.