Fork me on GitHub
#untangled
<
2016-11-23
>
wilkerlucio18:11:37

hello everyone

wilkerlucio18:11:42

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

wilkerlucio18:11:42

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

wilkerlucio18:11:51

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

wilkerlucio18:11:15

ps2: I'm moving this to here from #om because it may be a problem with Untangled read on client, I'm not sure