<div dir="ltr">Reviving this topic slightly, these were flagged up on the Julia forum<div><br></div><div><a href="https://github.com/aws/aws-lambda-runtime-interface-emulator">https://github.com/aws/aws-lambda-runtime-interface-emulator</a><br></div><div><br></div><div><span style="color:rgb(36,41,46);font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji";font-size:16px">The Lambda Runtime Interface Emulator is a proxy for Lambda’s Runtime and Extensions APIs, which allows customers to locally test their Lambda function packaged as a container image. </span> </div><div><br></div><div><a href="https://github.com/aws/aws-lambda-python-runtime-interface-client">https://github.com/aws/aws-lambda-python-runtime-interface-client</a><br></div><div><span style="color:rgb(36,41,46);font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji";font-size:16px">The Lambda Runtime Interface Client is a lightweight interface that allows your runtime to receive requests from and send requests to the Lambda service.</span> </div><div> <br></div><div><br></div><div><br></div><div> <br></div><div><br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, 25 Nov 2020 at 16:59, Tim Cutts <<a href="mailto:tjrc@sanger.ac.uk">tjrc@sanger.ac.uk</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div style="overflow-wrap: break-word;">
I think the 8 second limit is probably arbitrary. Lambda’s normal limit is 5 minutes. I presume Amazon did some UX work, and basically asked “what’s the maximum length of time your average user is willing to wait for an answer before they consider it a bad
experience”, and came up with 8 seconds. You’re not allowed to change that value, so they obviously take it seriously!
<div><br>
</div>
<div>While testing the skill I developed, I certainly found that the turnaround time when I had to perform a full remote data fetch was about 5 seconds. That’s long enough after asking Alexa the question that I start to think “is it going to reply?
is it working?” and that’s not a good experience, so my approach to that has been:</div>
<div><br>
</div>
<div>(a) cache the data fetched; the data is stored in session attributes, and persisted to S3. That cached copy provides a response which is within a second or two, a much nicer experience.</div>
<div><br>
</div>
<div>(b) when fetching fresh data, there’s a progressive response API which you can call asynchronously, while the slower task takes place. Now, that 5 second wait doesn’t feel so bad, because you’re listening to “Please wait while I ask for the latest
data” while the real work goes on in the background. Silence in a conversation feels really uncomfortable really quickly, as we all know.</div>
<div><br>
</div>
<div>Sorry, this is nothing to do with HPC or Beowulf, although kind of interesting from a UX perspective on voice-controlled systems.</div>
<div><br>
</div>
<div>Tim</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
<div><br>
<blockquote type="cite">
<div>On 25 Nov 2020, at 15:33, Lux, Jim (US 7140) <<a href="mailto:james.p.lux@jpl.nasa.gov" target="_blank">james.p.lux@jpl.nasa.gov</a>> wrote:</div>
<br>
<div>
<div style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none">
Interesting..<u></u><u></u></div>
<div style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none">
<u></u> <u></u></div>
<div style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none">
Where does the 8 second limit come from? (Rodeos and bull/bronc riding, where you only have to stay on for 8 seconds?) I’ve seen this 8 second thing in a bunch of places lately, and I wonder.. why not 7, or 10 or whatever? I find it hard to believe that someone
has a 3 bit counter in seconds (or worse, it’s a 33 bit counter counting nanoseconds or some such, and the limit is actually 8.589 seconds)<u></u><u></u></div>
<div style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none">
<u></u> <u></u></div>
</div>
</blockquote>
</div>
<br>
</div>
--
The Wellcome Sanger Institute is operated by Genome Research
Limited, a charity registered in England with number 1021457 and a
company registered in England with number 2742969, whose registered
office is 215 Euston Road, London, NW1 2BE.
</div>
</blockquote></div>