Open dandv opened 10 years ago
Yeah I totally agree with this - I'm often unclear what I'm looking at. It seems like one subscription will be blamed for a log wait time, when in reality it's surrounded by several others that are equally slow.
I agree. This should be a needy feature.
unsubscribe id is the subscriptionId. We should display the publication name along with it.
Arunoda Susiripala I curate Meteor Weekly - Check it out! http://meteorhacks.com/meteor-weekly/?utm_source=email-footer&utm_medium=email&utm_campaign=meteorweekly
On Sun, Jul 13, 2014 at 2:21 AM, David Weldon notifications@github.com wrote:
Yeah I totally agree with this - I'm often unclear what I'm looking at. It seems like one subscription will be blamed for a log wait time, when in reality it's surrounded by several others that are equally slow.
— Reply to this email directly or view it on GitHub https://github.com/meteorhacks/kadira/issues/13#issuecomment-48823716.
I think we can close this issue now :) https://kadira.io/blog/introducing-waittime-breakdown/
And here's a new guide of Managing Meteor Wait Time
I have a wait time of around 30 seconds (no idea how these things happen), across several operations. It would be great if Kadira could break down the time by operation. Not sure how to debug otherwise - those IDs for unsubscriptions, how can they be used? Are they just for Kadira's own debugging purpose?