3 ms·
“not necessarily terribly” is a little weasel-wordy, but it does, I think, give them enough space to consider hundreds of milliseconds as not a big deal. Edit:
by bee_rider 3y ago
“not necessarily terribly” is a little weasel-wordy, but it does, I think, give them enough space to consider hundreds of milliseconds as not a big deal.
Edit: see the responses for why “not necessarily terrible” is kind of annoying, now I have a comment that says there exists a use case where they care about it, and there exists one where they don’t.
- j45 3y agoIt might not be consistent to compare the entire request lifecycle instead of the original comment in only firing up.
- arp242 3y agoHundreds of milliseconds can be "not a big deal" depending on what your program is, how often it's run, etc. The last time I used CGI was for the "sign up to my newsletter" on my website; the endpoint for that would lock a file, append the email from the form, and close it. Even if that takes a second (which it didn't, more like 50ms) then ... that would actually be fine for this particular use case of a small newsletter. Of course for many other things it would be horrible. I think "not necessarily terrible" is a reasonable way to phrase things.
- surfingdino 3y agoDepends on the load levels or payment schedule. If we are talking about AWS Lambdas, hundreds of milliseconds are costing real money, which is why I write my Lambdas in Go instead of Python. That way we keep their exec time under 100ms which became unachievable with Python for the kind of code we're running. I love Python, but I don't love it enough to pay double or quadruple of what I pay for running Go code.
- acdha 3y agoYou’re right about the time is money dynamic but Lambda won’t hit this particular case because your imports will happen before the Lambda function starts receiving requests. I use that for things like retrieving SSM parameters and other setup work involving network requests.