Groups > comp.lang.python > #20199

Re: log and figure out what bits are slow and optimize them.

From	Kev Dwyer <kevin.p.dwyer@gmail.com>
Subject	Re: log and figure out what bits are slow and optimize them.
Date	2012-02-10 22:37 +0000
References	<a07666f2-a18b-4bf5-bbdc-8d7f74db09be@q8g2000pbb.googlegroups.com> <mailman.5654.1328877518.27778.python-list@python.org> <b0e0058a-9322-45a2-8707-c927e14ec714@u4g2000pbg.googlegroups.com>
Newsgroups	comp.lang.python
Message-ID	<mailman.5685.1328913452.27778.python-list@python.org> (permalink)

Show all headers | View raw

sajuptpm wrote:

> Hi,
> 
> Yes i saw profile module,
> I think i have to do function call via
> 
> cProfile.run('foo()')
> 
> I know, we can debug this way.
> 
> But, i need a fixed logging system and want to use it in production.
>       I think, we can't permanently include profile's debugging code
> in source code,
>      will cause any performance issue ??

*Any* instrumentation code is going to affect performance.

It's a trade-off that you need to analyse and manage in the context of your 
application.

Thread

log and figure out what bits are slow and optimize them. sajuptpm <sajuptpm@gmail.com> - 2012-02-10 04:30 -0800
  Re: log and figure out what bits are slow and optimize them. Arnaud Delobelle <arnodel@gmail.com> - 2012-02-10 12:38 +0000
    Re: log and figure out what bits are slow and optimize them. sajuptpm <sajuptpm@gmail.com> - 2012-02-10 04:56 -0800
      Re: log and figure out what bits are slow and optimize them. Kev Dwyer <kevin.p.dwyer@gmail.com> - 2012-02-10 22:37 +0000
        Re: log and figure out what bits are slow and optimize them. John Gordon <gordon@panix.com> - 2012-02-10 23:06 +0000
          Re: log and figure out what bits are slow and optimize them. sajuptpm <sajuptpm@gmail.com> - 2012-02-10 23:53 -0800
  Re: log and figure out what bits are slow and optimize them. Mark Lawrence <breamoreboy@yahoo.co.uk> - 2012-02-10 14:25 +0000

csiph-web