Ok cool

@cfleming: My own results http://numergent.com/2016-01/AWS-Lambda-Clojure-and-ClojureScript.html

those were pretty interesting. what version of Clojure were you using?

I'd be curious to see the timings with 1.8.0-RC5 (or soon 1.8.0) with a lambda compiled with direct linking

https://medium.com/@tjholowaychuk/introducing-apex-800824ffaa70

@alexmiller: 1.7, didn’t try with 1.8

Didn’t think to try, actually, I’ll give it a shot.

RC-4/5 improve startup time 10-15% is why I ask

and AOT compiling your lambda with direct linking may improve it more

The class is compiled AOT, but will look into RC5.

you can enable direct linking with -Dclojure.compiler.direct-linking=true

@alexmiller: Will need more thorough testing, but right now averages are about the same with 1.8 RC5.

thx, probably dwarfed by other costs then

@martinklepsch: I saw Apex on HN, it looks very nice.

Tailing CloudWatch logs is worth the price of admission alone.

@ricardo: You’re measuring total RTT there from the API client, right?

Is the API client external to AWS, i.e. you’re not invoking from EC2?

Also, it looks like you’re not calling any other AWS services, correct?

@cfleming: It’s the billed duration, actually - I should have clarified that. The rest is correct, as far as the test numbers go. It’s also the time for invoking them directly, not through API Gateway. Full roundtrip through API gateway is a bit erratic - adds between 600ms-1200ms.

Thanks for bringing it up, going to add a note to the article.

@ricardo: Great, thanks for the details. Just working up my client now.

@ricardo: How many iterations did you run for the stable times?

@ricardo: Also, did you get the billed duration from CloudWatch automatically somehow, or by hand from the logs?