This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-11-23
Channels
- # admin-announcements (1)
- # arachne (3)
- # aws (1)
- # bangalore-clj (2)
- # beginners (209)
- # boot (81)
- # capetown (2)
- # cider (16)
- # clara (13)
- # cljsjs (16)
- # cljsrn (6)
- # clojure (217)
- # clojure-czech (1)
- # clojure-greece (4)
- # clojure-italy (3)
- # clojure-korea (3)
- # clojure-russia (3)
- # clojure-sg (3)
- # clojure-spec (104)
- # clojure-uk (23)
- # clojurescript (7)
- # component (7)
- # cursive (18)
- # datomic (12)
- # devcards (34)
- # dirac (17)
- # editors (3)
- # emacs (1)
- # events (1)
- # hoplon (62)
- # immutant (12)
- # incanter (1)
- # jobs (1)
- # klipse (2)
- # ldnclj (1)
- # luminus (1)
- # mount (1)
- # off-topic (8)
- # om (50)
- # onyx (46)
- # parinfer (5)
- # pedestal (4)
- # perun (2)
- # reagent (1)
- # rum (1)
- # schema (5)
- # specter (30)
- # untangled (5)
- # vim (46)
hello everyone
I'm experiencing some performance issues with recursive queries, something seems off, after doing a simple transaction (just changing a string) this is getting on the console: https://www.dropbox.com/s/u5lzdtwxrk87ydp/Screenshot%202016-11-23%2015.13.00.png?dl=0
seems like it's triggering the read multiple times, I don't understand why. did someone found anything similar or have an idea about what might be going on? I believe it's related to recursive queries because removing that query part makes it work normal
ps: the recursive results are in the range of about 3 items, each going 3 4 levels deep (around 12 18 iterations total), so, not enough to justify this amount of lagging
ps2: I'm moving this to here from #om because it may be a problem with Untangled read on client, I'm not sure