This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-04-03
Channels
- # arachne (31)
- # aws (9)
- # bangalore-clj (7)
- # beginners (46)
- # boot (18)
- # cider (21)
- # cljs-dev (8)
- # clojure (154)
- # clojure-dusseldorf (5)
- # clojure-filipino (3)
- # clojure-ireland (4)
- # clojure-italy (9)
- # clojure-russia (6)
- # clojure-spec (6)
- # clojure-uk (52)
- # clojureremote (3)
- # clojurescript (173)
- # clojurewest (14)
- # cursive (24)
- # data-science (2)
- # datomic (18)
- # defnpodcast (1)
- # devcards (1)
- # hoplon (4)
- # instaparse (29)
- # jobs (2)
- # juxt (1)
- # leiningen (3)
- # lumo (78)
- # off-topic (46)
- # om (9)
- # onyx (42)
- # pedestal (33)
- # perun (3)
- # re-frame (9)
- # reagent (6)
- # slack-help (5)
- # spacemacs (2)
- # specter (6)
- # unrepl (157)
- # untangled (99)
- # yada (32)
has anyone messed around with Dynamodb Streams? It looks like it is super super slow to call my lambdas on puts (the latency of the put itself is very low). It takes 37 seconds!!
in my experience, going from lambda <-> any other aws service is kind of slow. 37 seconds seems excessive, though.
@bhagany thanks, basically I am doing a put in DynamoDB and triggering the same function using a Dynamo Stream trigger...if I do the diff between the put and the time when the triggered lambda starts I get 37 seconds...but maybe this is not an effective way to test this thing
@richiardiandrea how big is your jar
I am using JavaScript, the lamdba is very little...Just a pic to in DynamoDB basically
Oh cool stuff ;)