On Tue, 28 Nov 2023, 15:26 Filbert, wrote:
> crickets...sigh...
>
Is your question is more about profiling Python (async) code than anything
specifically to do with Django?
If so, then obviously Google is likely a good place to start.
If not, and your issue is more about support for async from
crickets...sigh...
On Monday, November 27, 2023 at 11:29:37 AM UTC-5 Filbert wrote:
> We are heavily using Django Channels async consumers and haven't found a
> way instrument for performance profiling.
>
> We've tried NewRelic, but per their developers say they don't have support
> for Django
We are heavily using Django Channels async consumers and haven't found a
way instrument for performance profiling.
We've tried NewRelic, but per their developers say they don't have support
for Django Channels.
We run certain websocket connections through Gunicorn, Uvicorn,
Channels-Async and
Thanks a bunch :-) Got it working in python 3 with minor tweaking.
Thomas
On Thu, Mar 14, 2013 at 3:09 PM, Shawn Milochik wrote:
> I use this and it's great. I haven't tried it with Python 3, but it's
> all standard library stuff.
>
> I tweaked mine a bit so it dumps the profile files to my temp
I use this and it's great. I haven't tried it with Python 3, but it's
all standard library stuff.
I tweaked mine a bit so it dumps the profile files to my temp folder
instead of the way it works by default. That's because I wanted to
profile AJAX calls, keep multiple runs for the same sites for A/
I've tried to find middleware for django or other methods of profiling
my django apps, but most of them seem to use the hotspot module and
since I use Python 3 and there's no hotspot module in Python 3 I was
wondering if anybody out there had a working profiler for django
compatible with Python 3?
On Wed, Apr 4, 2012 at 4:07 AM, Tom Evans wrote:
> One pretty cool method I've used for live debugging in the past is to
> 'log' to rabbitmq (Note - not celery - raw amqp), and send messages to
> a logging exchange. You can use a topic key so that different
> processes can be distinguished.
a sim
On Tue, Apr 3, 2012 at 11:25 PM, Andre Terra wrote:
> Hey Javier,
>
> Thanks for the reply. My problem with the logs in the past was that they
> tended to make the task even slower (due to recursion) but I guess that's
> probably because I didn't call the logging from the appropriate places in
> t
On Tue, Apr 3, 2012 at 5:25 PM, Andre Terra wrote:
> To make things a little more complicated, the task involves writing a large
> amount of data to a temp database, handling it and then saving some
> resulting queries to the permanent DB. This makes it a tad harder to analyze
> what goes on in th
Hey Javier,
Thanks for the reply. My problem with the logs in the past was that they
tended to make the task even slower (due to recursion) but I guess that's
probably because I didn't call the logging from the appropriate places in
the code.
To make things a little more complicated, the task inv
On Tue, Apr 3, 2012 at 8:21 AM, Andre Terra wrote:
> I have some complex and database intensive asynchronous tasks running under
> celery which take a LONG time to complete and I'd just love to be able to
> keep track of the queries they generate in order to optimize and possibly
> remove the bigg
While I know of the two methods mentioned by Anssi, I've often wondered how
to profile my code from a project level.
I have some complex and database intensive asynchronous tasks running under
celery which take a LONG time to complete and I'd just love to be able to
keep track of the queries they
On Wed, Oct 12, 2011 at 6:49 PM, <
michael.pimmer@boehringer-ingelheim.com> wrote:
> **
>
> - django-debug-toolbar with profiling from
> http://backslashn.com/post/505601626/ - too fine-grained:
>I do not want to know that 138752 calls to
> python2.6/posixpath.py:129(islink) take 0.858 sec
A good place to start is using django-debug-toolbar and taking a look at the
queries generated for each view, so that you know what's taking long. There
are tools for monitoring database performance, but I have no experience with
them, so I'll leave it to other members in this list to make the
reco
The django application I am working on is very slow on the server-side, and I
want to know why.
The essence is to identify which code-parts of processing one request take
most time.
The app runs with mod_wsgi on Apache, here is what I tried:
- django-timelog: the information logged is too unspeci
I tried appending -m cProfile -o project.profile to this call:
/usr/bin/python manage.py runfcgi...
but i got an error saying can't open cProfile - no such file or
directory. is this even the right place to call cProfile?
the other option would be to modify this:http://code.djangoproject.com/
b
the page here: http://code.djangoproject.com/wiki/ProfilingDjango
mentions profiling with hotshot & mod_python, or wsgi & cprofile. the
stuff here: http://www.djangosnippets.org/snippets/605/ is also for
hotshot, not cprofile. i'm not sure how to get this going with
fastcgi - which i'm starting
I found this Profiling Middleware earlier today. Haven't had a chance
to test drive it yet, but it might be what you're looking for:
http://www.djangosnippets.org/snippets/186/
On Jun 8, 10:17 am, Richard Phelps <[EMAIL PROTECTED]> wrote:
> I'd appreciate guidance as to how to go about identifyin
I'd appreciate guidance as to how to go about identifying slow-
running portions of python code in my extensively customised django
applications suite. Most posts I've found address the probably more
important issues that relate to web page serving and database
efficiency issues, but as a r
On 5/24/07, patrick k. <[EMAIL PROTECTED]> wrote:
>
> thanks david. it´s working now (although I´m having problems
> interpreting the stats, but that´s another question).
This should help:
http://www.rkblog.rk.edu.pl/w/p/django-profiling-hotshot-and-kcachegrind/
--~--~-~--~~-
thanks david. it´s working now (although I´m having problems
interpreting the stats, but that´s another question).
for everyone who´s reading this, here´s more about the python-
profiler on debian:
http://mail.python.org/pipermail/tutor/2005-March/036677.html
thanks,
patrick
Am 24.05.2007 u
Patrickk,
On 24 May 2007, at 2:15 pm, patrickk wrote:
I´m just trying to do some profiling based on
http://code.djangoproject.com/wiki/ProfilingDjango
when trying to import hotshot.stats I´m getting this:
Traceback (most recent call last):
File "", line 1, in ?
File "/usr/lib/python2.4/
I´m just trying to do some profiling based on
http://code.djangoproject.com/wiki/ProfilingDjango
when trying to import hotshot.stats I´m getting this:
Traceback (most recent call last):
File "", line 1, in ?
File "/usr/lib/python2.4/hotshot/stats.py", line 3, in ?
import profile
Import
23 matches
Mail list logo
