Show HN: Silk, a profiling tool for Django

Probably not a good idea to keep your profiler open to the world as long as you allow reading from arbitrary files. After a bit of fiddling around I was able to read your secret key from the settings file. It starts with 'es!b3'. And your soundcloud password. Sorry.

Very cool, this seems much nicer than using hotshot to profile Django.<p>I&#x27;m a little confused by this page though: <a href="http://mtford.co.uk/silk/request/1907/profiling/" rel="nofollow">http:&#x2F;&#x2F;mtford.co.uk&#x2F;silk&#x2F;request&#x2F;1907&#x2F;profiling&#x2F;</a>. Why is wrapped_target listed so many times for a single blog post query? Is there a hierarchy to the profile calls that&#x27;s not shown? Oh, does it go deepest level to highest level calls?

Looks very interesting! We currently use django debug toolbar for profiling, which seems to have a lot of overlap. I like how Silk stores the profiles of multiple requests - that seems to be a nice differentiator. What else? Thanks for the awesome contribution to the Django community!

This is a really great tool, massive fan, made some good use of it in the ~15 hours since I installed it yesterday evening. Are you aware it seems to bork the admin interface?<p>If, after installing Silk, I use admin to update a record, I get &quot;You cannot access body after reading from request&#x27;s data stream&quot; - this applies across all admin models and pages. It&#x27;s not really that big a deal, as I rarely use the admin pages now, but it might have knock-on effects that I haven&#x27;t seen yet. (Commenting out Silk in the installed apps list clears the problem up straight away.)<p>I&#x27;ll ping you an email with the stack trace.

Looks really nice.<p>Have you thought that instead of sending the results to elasticsearch? Instead of using something like newrelic this could take it&#x27;s place..

I wrote <a href="https://github.com/rory/django-sql-inspector" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;rory&#x2F;django-sql-inspector</a> a django app to profile SQL queries done in multiple pages, including showing stack trace of where it&#x27;s being called. You can find out which function(s) are responsible for long SQL requests.

What is the overhead (roughly) for this guy? I do absolutely <i>love</i> the idea of using elasticsearch for this instead of a traditional database.<p>Using celery or django-rq to delay the processing also seems reasonable.

After reading through this intro, it isn&#x27;t clear to me if I can use the decorator or context manager to profile code outside the request&#x2F;response cycle.<p>Any ideas if that&#x27;s the case?

For people interested in production monitoring I&#x27;ve created <a href="https://appenlight.com" rel="nofollow">https:&#x2F;&#x2F;appenlight.com</a> - and our python middleware will integrate and start timing django applications without any code changes required (except 3 lines to load middleware itself).<p>@mtford great job!

Thanks for posting this! Could you add a download link somewhere?

absolutely great tool!