-
-
Notifications
You must be signed in to change notification settings - Fork 339
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Allowing profiling outside of the request/response cycle #3
Comments
@auvipy Not sure if django-channels is within the purview of this library. Not against it though. The issue becomes volume. Since channels is meant for websockets it will definitely be high-volume. |
OK. we can re think about django channels at a later stage. |
+1 |
Silk is an awesome tool, it would be great to use it for profiling celery or other async tasks that happen outside the request/response cycle. |
We have a use case where this feature would be extremely useful. Our application has a lot of long-running asynchronous "tasks" using RQ. Currently, django-silk can't help us because none of the hard work is being done within the scope of a request. Each individual task is very intensive but there are not that many of them, relatively speaking, so it's not a "high volume" problem. A lot of applications use Celery, also. Same principle. I would love to be able to use Silk to debug our task performance. |
any prospective API wor workflow do you have in mind how should be the DevUX for the API of that profiler to profile celery/ etc with or outside of django req/resp cycle? |
Hi, |
Fix demo in python 3
Do not want to necro something, is there a way to achieve this somehow? |
FYI I found this GitHub gist that you can use to run django-silk against arbitrary functions not wrapped in APIs. This was a good-enough workaround for me to debug some performance challenges, although it would be fantastic to see something supported by django-silk in the future. |
e.g. a profile should not have to be associated with a request, perhaps by detecting that no request is in process and then committing profile data on the fly if that's the case.
The text was updated successfully, but these errors were encountered: