When the app has been idle for a little while some...
# prisma-whats-newj
joar
05/22/2017, 11:02 AMWhen the app has been idle for a little while some (simple) queries take 10+ seconds to resolve. Can we pay to never have to experience cold starts? 😛 If a user would have to wait for that long they would quit
n
nilan
05/23/2017, 8:45 AM@joar this is unexpected behaviour, is that reproducible consistently?
j
joar
05/23/2017, 9:40 AMIt used to happen consistently every time in the morning when I hadnt made any requests for a while, and then subsequent requests were ~5 times faster, however now there’s a lot more people working on the platform and using it so there is no certain scenario anymore where it happens every time
joar
05/23/2017, 9:41 AMI can add some request time tracking to the app and try to find a pattern
n
nilan
05/23/2017, 9:42 AMwe identified and fixed two performance issues late last week - have you encountered this issue since then again?
j
joar
05/23/2017, 9:44 AMYes, I sat through a very slow request right before sending that message
joar
05/23/2017, 9:45 AMbtw on another note: looks like the issue I was seeing yesterday is related to nested mutations, like that other issue was discussing
joar
05/23/2017, 9:45 AMoh sorry, just noticed you replied to that issue. I’ll try out what you said
n
nilan
05/23/2017, 9:45 AMAlright, if you have more information on a potential pattern here that would be very useful!
nilan
05/23/2017, 9:46 AMYea, the other issue reports that it works for the top level mutation but not for the nested one, is that the same behaviour you're experiencing?
j
joar
05/23/2017, 10:15 AMYep! Confirmed it just now
n
nilan
05/23/2017, 10:21 AMThanks! I'll let both reports open as they both give good information