AWS Introducing Provisioned Concurrency for Lambda Functions

Post by scarface74 » Thu, Dec 05, 2019, 1:59 AM UTC

munns wrote: post #52

scarface74 wrote: post #50

Earlier quoted context omitted.

The cold start from using lambda has a number of causes 1. the time to initialize the VM 2. the time to create an ENI if you are connecting to a VPC[1](until the NAT alternative rolls out globally) 3. the time to initialize your language runtime (Java seems to be the worse, scripting languages the best) 4. any program initialization done outside of your handler that runs once per cold start of your lambda runtime. A…

Fwiw new networking for VPC is completely rolled out for all public regions now. (#2) (and thank you, its called "Attached to a VPC" and not in :) ) This covers you straight through 4. Now it's possible that your execution environment could be sitting for sometime waiting for any action and so pre-handler DB connections and things like that might need to be tweaked in this model. Thanks, - munns

Post by macintux » Tue, Dec 10, 2019, 2:19 PM UTC

msftie wrote: post #68

macintux wrote: post #61

Earlier quoted context omitted.

There are other oddities too. For example, to get a layer name from a lambda definition, the simplest/most robust process I can define: 1 Retrieve all layers with list_layers and index them by ARN 2 Retrieve all function metadata 3 For each function metadata item, extract all layer version ARNs 4 For each layer version ARN, call get_layer_version_by_arn 5 Extract the layer ARN from that result 6 Use that layer ARN to…

Layer Name and Layer Arn (the Layer Version Arn without a version suffix) are interchangeable in APIs that require a Layer Name parameter. I understand that you're trying to extract the "LayerName" field returned in the API response in ListLayers, but you can do it more concisely. If you just need the Layer Arn to call other APIs: a) You could eliminate steps 1 and 6, and use the Layer Arn value from 5 to call APIs t…