This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-01-20
Channels
- # adventofcode (8)
- # aleph (2)
- # announcements (10)
- # aws (5)
- # aws-lambda (2)
- # babashka (23)
- # beginners (23)
- # biff (9)
- # calva (4)
- # cider (8)
- # clj-kondo (21)
- # clojure (77)
- # clojure-boston (1)
- # clojure-dev (50)
- # clojure-europe (36)
- # clojure-gamedev (3)
- # clojure-nl (1)
- # clojure-norway (3)
- # clojure-spec (33)
- # clojure-uk (3)
- # clojurescript (22)
- # core-async (3)
- # cursive (10)
- # datahike (18)
- # datalevin (1)
- # datascript (9)
- # deps-new (21)
- # emacs (11)
- # events (1)
- # graphql (11)
- # guix (26)
- # java (7)
- # jobs (3)
- # lsp (12)
- # malli (6)
- # pathom (33)
- # pedestal (3)
- # polylith (15)
- # reagent (5)
- # releases (3)
- # remote-jobs (1)
- # scittle (9)
- # sql (27)
- # tools-build (9)
- # vim (7)
this question can be relevant to GraphQL 🙏
aws-api response is extremely fast with small requests as I see. Plus, intervals are 50ms for all.
Shameless plug: I wrote https://github.com/vlaaad/plusinia to get rid of waiting for intervals in superlifter
intervals can be affected to response time but that lags looks weird though.
@U47G49KHQ Thank you for sharing! I’ve starred and looked into it ! hope I want to consider it shortly.
Hmm.. :thinking_face:
Also, I can recommend trying a profiler with a flame graph to see where is the time spent while the request is processed. E.g. https://github.com/clojure-goes-fast/clj-async-profiler/
Thanks a lot. I’ll use it too. At the same time, I have to dive into superlifter’s usage first.