Fork me on GitHub
#aws
<
2016-01-15
>
ricardo09:01:52

@clojuregeek Not seeing the issue myself, but in case I do… was it the expired credentials issue?

ricardo09:01:35

And since we’re on the topic of lambda… is anyone using Clojure for lambdas? I’ve been doing some tests on Clojure vs. ClojureScript, and the warm up hit on the Clojure lambdas is significant.

jaen09:01:38

I think I remember something about Cursive licenses using lambdas with Clojure, but might be misremembering.

ricardo10:01:52

Hmm, thanks @jaen, I’ll ping @cfleming

ragge10:01:22

@ricardo: we use clojure for a few lambda functions, see: https://github.com/uswitch/lambada

ragge10:01:11

@ricardo: warm up hit comes up everytime, only a (potential) problem on the first invocation

ragge10:01:27

@ricardo: so depends very much on your use case

ricardo10:01:14

@ragge: Thanks, I actually wrote my clj tests with lambada. Main cause for concern is that the first call seems to take on average ~9s, and API Gateway times you out at 10s.

ragge10:01:43

yeah, for that kind of use case it might be problematic (~9s sounds slooow though)

ragge10:01:57

i use it for batch processing s3 and similar

ricardo10:01:02

It’s calling to a couple external APIs which probably take 1-2s to complete. The rest should be its own time. What’s the usual memory you set up for your functions? I understand AWS scales the CPU accordingly, but haven’t seen a relation table anywhere.

ricardo10:01:01

That was for 256MBs. At 1024 it warms up faster.

ragge10:01:04

varies, but jvms like plenty of ram

ricardo10:01:36

That is… I haven’t seen a description for how the proportional scaling goes. In my test case the memory use is low, so it’s probably the CPU that’s affecting startup time.

ragge10:01:04

could be, docs are definitely lacking in many areas

ricardo10:01:23

Thanks for the datapoint @ragge

luposlip10:01:47

Managed to get Datomic up and running on AWS ECS in a docker container. And I can connect to it from the EC2 host (so managed to get both host and alt-host set correctly, as well as the security settings of the AWS setup).

luposlip10:01:59

Small POC container showing the trick with the IP adresses: https://github.com/enterlab/docker-aws-ecs-env

meow13:01:13

sharing is caring

clojuregeek15:01:20

@ricardo: yes i think it was, also I think my aws-cli was not set right which is what cljs-lambda uses