This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-07-21
Channels
- # aws (14)
- # babashka (35)
- # beginners (163)
- # boot (2)
- # calva (5)
- # cider (30)
- # clojure (143)
- # clojure-colombia (1)
- # clojure-europe (5)
- # clojure-nl (11)
- # clojure-spec (1)
- # clojure-uk (16)
- # clojurescript (71)
- # community-development (2)
- # conjure (1)
- # cursive (6)
- # datomic (30)
- # duct (4)
- # figwheel-main (11)
- # fulcro (28)
- # graalvm (3)
- # graphql (23)
- # hoplon (36)
- # jackdaw (24)
- # kaocha (16)
- # lambdaisland (1)
- # leiningen (4)
- # luminus (3)
- # meander (4)
- # observability (1)
- # off-topic (10)
- # pathom (5)
- # re-frame (27)
- # reitit (7)
- # remote-jobs (1)
- # sci (17)
- # shadow-cljs (22)
- # spacemacs (14)
- # sql (61)
- # testing (3)
- # tools-deps (27)
- # vim (2)
- # xtdb (18)
- # yada (2)
Hi everybody, off-topic AWS question. Any of you have experienced terrible response times after putting your EC2 through an application LB? We had this thing running fine in a t2 micro. As soon as we put it behind the LB performance dropped. We had another case were we just removed availability zones from the LB that had no instances on them. But this time I just can't get what's going on.
profiling the application/JVM profiling the machine monitor the load balancer (in rough priority order of things to investigate)
What's weird is this happens as soon as we put this thing behind the LB. Otherwise things run just fine.
Yup, from 1-3 seconds to up to a minute. Seems like the first requests you make "warm up" something, after that the application works fine for a while and then takes a dive again.
my $0.02; it is too early to speculate -- find some data about what is going on, then make a hypothesis