Re:AWS Lambda pricing now per ms
by jeffbee on Tuesday December 01, 2020 @12:51PM
(#25267658)
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)?
[ Parent
| on HN ]
Re:AWS Lambda pricing now per ms
by londons_explore on Tuesday December 01, 2020 @01:30PM
(#25268142)
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.