Query time-outs

[jacksonofalltrades]

After the amount of data collected is larger than a certain size (not exactly sure what that size is), the silk admin page stops responding and in fact eventually just gets an empty response. I've spent a lot of time trying to figure out how this is possible, and the best I can come up with is that some of the aggregate queries take way too long to return.

Our best strategy at this point is to manually edit the queries and make them less time-consuming. Any other suggestions?

[avelis]

@jacksonofalltrades Depending on your request volume, a little bit of tuning can go a long way. I suggest either lowering the SILKY_INTERCEPT_PERCENT value to some number below 50 (perhaps 25). You could also use the SILKY_INTERCEPT_FUNC that can determine which requests are worthy of logging to django-silk.

[avelis]

@jacksonofalltrades If you find enhancements to performance of certain aggregation queries, I am always open to PR's.

[jacksonofalltrades]

Great, thank you for your quick response, we can try those!

So just to clarify, is the reason for those two configs precisely because capturing everything is an issue for others as well? That would make me feel better :)

[avelis]

It's hard to say for sure, I would have to search through the repo's history. However, having granular control to determine what to collect and at what percentage is helpful in this scenario.

Rest easy @jacksonofalltrades you are likely not alone. :-)

[avelis]

@jacksonofalltrades If the above suggestions work for you, I am going to close this issue.