Re: Performance profiling Django Channels async consumers

[Shaheed Haque]

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 tools like the
Django Debug Toolbar, it might be worth being explicit about that.

(FWIW, we faced a similar issue with trying to analyse db usage from
Celery, and ended up brewing some custom tooling loosely based on the
Django Debug Toolbar output).




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 Channels.
>>
>> We run certain websocket connections through Gunicorn, Uvicorn,
>> Channels-Async and are looking for anyway to instrument the code to get a
>> better analysis of what code is hogging the event loop.
>>
>> Advice appreciated.
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/9e05ae10-ca38-4853-b875-d4594bda394en%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAHAc2jdNB8xh7Rk8q0uLq%3DfEuoyvA38ZgutMhAdEn6KBrdez%3DA%40mail.gmail.com.

Re: Performance profiling Django Channels async consumers

[Filbert]

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 Channels.
>
> We run certain websocket connections through Gunicorn, Uvicorn, 
> Channels-Async and are looking for anyway to instrument the code to get a 
> better analysis of what code is hogging the event loop.
>
> Advice appreciated.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/9e05ae10-ca38-4853-b875-d4594bda394en%40googlegroups.com.

Performance profiling Django Channels async consumers

[Filbert]

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 are looking for anyway to instrument the code to get a 
better analysis of what code is hogging the event loop.

Advice appreciated.

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/8769b0fc-f23c-44ac-8217-7c3a1da4d379n%40googlegroups.com.

Re: Profiling django apps using Python 3? No hotspot module.

[Thomas Weholt]

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 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/B
> comparisons, and because I don't have to know in advance I'm going to
> want to profile something. I can always just look at the file for
> anything I just did.
>
> https://gist.github.com/1229681
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to django-users+unsubscr...@googlegroups.com.
> To post to this group, send email to django-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-users?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>



-- 
Mvh/Best regards,
Thomas Weholt
http://www.weholt.org

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Profiling django apps using Python 3? No hotspot module.

[Shawn Milochik]

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/B
comparisons, and because I don't have to know in advance I'm going to
want to profile something. I can always just look at the file for
anything I just did.

https://gist.github.com/1229681

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Profiling django apps using Python 3? No hotspot module.

[Thomas Weholt]

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?

If not I'll try to port one of the ones I've found but why re-invent the wheel?

-- 
Mvh/Best regards,
Thomas Weholt
http://www.weholt.org

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Profiling Django (WAS Django database-api)

[Javier Guerra Giraldez]

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 similar thing can be done with ZeroMQ, with the advantage of not
needing a mq daemon.  but i guess Andre already uses rabbitmq, so
yours would be the easiest way.

-- 
Javier

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Profiling Django (WAS Django database-api)

[Tom Evans]

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
> the code.
>
> 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 the first part of the code.
>
> I'll try logging again over the weekend and see how that works.. I just wish
> there were third party apps and tools for debugging this sort of problem.
>
> Thanks again for your input.
>
> Cheers,
> AT

Hi Andre

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.

Then, if you want to see the running logs of what is happening, you
simply attach a dumb listener that binds a queue to that exchange,
receives the message and prints it out. If you're no longer
interested, detach the listener, and rabbitmq will just discard the
messages with little overhead.

If you want to do stuff with AMQP, I'd recommend pika [1], which is
just brilliant and easy to understand (other amqp libraries, less
so!).

Cheers

Tom

[1] http://pika.github.com/

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Profiling Django (WAS Django database-api)

[Javier Guerra Giraldez]

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 the first part of the code.

i haven't had that kind of problem, but these are the things i would try:

- time-limiting logs.  if the last call was too recent, just discard
the message (for some log levels, those used in the inner loops)

- send the logfiles to fast devices (maybe even in ram, like tmpfs in
Linux) and aggressively rotate them (so they don't accumulate
needlessly)

- log to a fast database (like Redis) and do automated analysis every
hour or maybe even every minute, discarding the raw log entries.

- log to a listening process that checks if each (time limited) entry
is out of the ordinary. if so, keep it for analysis. if not, discard
it.  'ordinary' could mean if some indicator is growing or reducing as
expected, or just changed from the last, or stable, or whatever you
could expect from your intended calculations.

-- 
Javier

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Profiling Django (WAS Django database-api)

[Andre Terra]

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 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 the first part of the code.

I'll try logging again over the weekend and see how that works.. I just
wish there were third party apps and tools for debugging this sort of
problem.

Thanks again for your input.

Cheers,
AT

On Apr 3, 2012 3:47 PM, "Javier Guerra Giraldez"  wrote:
>
> 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 biggest bottlenecks.
>
> the easiest would be to write detailed logs, which _can_ be analysed
> in real time, not only 'after the fact'.
>
> my second idea would be to hack the log output so instead of writing
> to a file, it would store messages (probably with some structure) to
> some comfortable database.  I'd use Redis, but i guess MongoDB or even
> an SQL-based DB could work too.  then you can easily filter and
> aggregate times according to task type, when it happened, etc.
>
> --
> Javier
>
> --
> You received this message because you are subscribed to the Google Groups
"Django users" group.
> To post to this group, send email to django-users@googlegroups.com.
> To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Profiling Django (WAS Django database-api)

[Javier Guerra Giraldez]

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 biggest bottlenecks.

the easiest would be to write detailed logs, which _can_ be analysed
in real time, not only 'after the fact'.

my second idea would be to hack the log output so instead of writing
to a file, it would store messages (probably with some structure) to
some comfortable database.  I'd use Redis, but i guess MongoDB or even
an SQL-based DB could work too.  then you can easily filter and
aggregate times according to task type, when it happened, etc.

-- 
Javier

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Profiling Django (WAS Django database-api)

[Andre Terra]

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 generate in order to optimize and possibly
remove the biggest bottlenecks.

"Real time" updates would be great, but I can settle for after-the-fact
logs. I know of django-debug-toolbar [0] but since these aren't happening
in a view, I'm not sure that app can help.

Any suggestions? Thanks in advance!

Cheers,
André Terra

[0] http://pypi.python.org/pypi/django-debug-toolbar
 On Apr 3, 2012 6:13 AM, "KasunLak"  wrote:

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Profiling Django

[Venkatraman S]

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 seconds. I want to know in
> which views / functions it happens.
>
Is the best way to profile, for if yours is a db centric app(which is in
most cases), a bad join can cause thousands of queries.
The ORM query might look harmless, but the sqls can cause a domino.

-V

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Profiling Django

[Andre Terra]

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
recomendations. Maybe go after disk read/write monitoring if you have access
to that?

When possible, moving the big functions in your code to asynchronous celery
tasks [1] will nearly always speed things up.

If you're doing big (hundreds of thousands of rows) db calls, try using DSE
[2]

[1] http://readthedocs.org/docs/django-celery/en/latest/
[2] http://pypi.python.org/pypi/dse


Cheers,
AT


On Wed, Oct 12, 2011 at 10:19 AM, <
michael.pimmer@boehringer-ingelheim.com> wrote:

> **
>
> 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 unspecific and
> high-leveled. I want to know which functions and parts of a view require
> most time. (moreover, analyze_timelog doesn't work here)
> - 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 seconds. I want to know in
> which views / functions it happens.
> - profiling with wsgiref, like described in
> https://code.djangoproject.com/wiki/ProfilingDjango#no1 - looks like (and
> probably is?) exactly the same output as the django-debug-toolbar with
> profiling: too fine-grained, I want to get an overview, not the pure
> low-level calls.
>
> What is your preferred way to analyze/profile the performance of
> django-applications?
>
> thanks,
> Michael
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To post to this group, send email to django-users@googlegroups.com.
> To unsubscribe from this group, send email to
> django-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Profiling Django

[michael.pimmer.ext]

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 unspecific and high-leveled.
I want to know which functions and parts of a view require most time.
(moreover, analyze_timelog doesn't work here)
- 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 seconds. I want to know in
which views / functions it happens.
- profiling with wsgiref, like described in
https://code.djangoproject.com/wiki/ProfilingDjango#no1 - looks like (and
probably is?) exactly the same output as the django-debug-toolbar with
profiling: too fine-grained, I want to get an overview, not the pure
low-level calls.

What is your preferred way to analyze/profile the performance of
django-applications?

thanks,
Michael

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: profiling django with fastcgi & cprofile?

[skunkwerk]

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/
browser/django/trunk/django/core/handlers/profiler-hotshot.py
to work with cProfile instead.  what would I replace the
ModPythonHandler with (i'm using fastcgi)

thanks again

On May 1, 11:31 am, skunkwerk <[EMAIL PROTECTED]> wrote:
> 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 through an init.d script like so:
>
> start-stop-daemon --start --exec /usr/bin/python $SITES_PATH/$SITE/
> manage.py runfcgi method=threaded host=$HOST port=$PORT pidfile=
> $RUNFILES_PATH/$SITE.pid --pidfile
>
> would i just need to pass an argument to get it to go through
> cProfile, or write/adapt an entire script?
>
> thanks
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---

profiling django with fastcgi & cprofile?

[skunkwerk]

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 through an init.d script like so:

start-stop-daemon --start --exec /usr/bin/python $SITES_PATH/$SITE/
manage.py runfcgi method=threaded host=$HOST port=$PORT pidfile=
$RUNFILES_PATH/$SITE.pid --pidfile

would i just need to pass an argument to get it to go through
cProfile, or write/adapt an entire script?

thanks
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---

Re: Profiling django site

[[EMAIL PROTECTED]]

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 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 relatively new python programmer I'd like
> to be more sure that my own code  is not slowing things more than
> need be. Is there a profiler to measure time spent in functions?
>
> Richard Phelps


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---

Profiling django site

[Richard Phelps]

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 relatively new python programmer I'd like  
to be more sure that my own code  is not slowing things more than  
need be. Is there a profiler to measure time spent in functions?


Richard Phelps


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---

Re: profiling django / import error: no module named profile

[Jeremy Dunck]

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/

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---

Re: profiling django / import error: no module named profile

[patrick k.]

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 um 17:13 schrieb David Reynolds:

> 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/hotshot/stats.py", line 3, in ?
>>  import profile
>> ImportError: No module named profile
>>
>> any ideas?
>>
>
> If you're on Debian or Ubuntu:
>
> # aptitude install python-profiler
>
> Thanks,
>
> David
>
> -- 
> David Reynolds
> [EMAIL PROTECTED]
>
>


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---

Re: profiling django / import error: no module named profile

[David Reynolds]

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/hotshot/stats.py", line 3, in ?
 import profile
ImportError: No module named profile

any ideas?



If you're on Debian or Ubuntu:

# aptitude install python-profiler

Thanks,

David

--
David Reynolds
[EMAIL PROTECTED]




smime.p7s
Description: S/MIME cryptographic signature

profiling django / import error: no module named profile

[patrickk]

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
ImportError: No module named profile

any ideas?

thanks,
patrick



--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---