Raf wrote:
> On Wed, 24 Jan 2007, Perrin Harkins wrote:
>
>>On 1/24/07, Raf <[EMAIL PROTECTED]> wrote:
>>
>>>The code base I'm profiling is very big, monolithic and convoluted. I
>>>felt that level of granularity given by smallprof would probably give me
>>>more coverage - which I believe I need.
On Wed, 24 Jan 2007, Perrin Harkins wrote:
> On 1/24/07, Raf <[EMAIL PROTECTED]> wrote:
> > The code base I'm profiling is very big, monolithic and convoluted. I
> > felt that level of granularity given by smallprof would probably give me
> > more coverage - which I believe I need.
>
> Usually tha
On 1/24/07, Raf <[EMAIL PROTECTED]> wrote:
The code base I'm profiling is very big, monolithic and convoluted. I
felt that level of granularity given by smallprof would probably give me
more coverage - which I believe I need.
Usually that's the reason you use DProf -- it gives you the big
pict
Hi Philip,
On Tue, 23 Jan 2007, Philip M. Gollucci wrote:
> Raf wrote:
> > Apologies for the X-post. It seemed appropriate.
> >
> Mot off the top of my head, why are you using Apache::SmallProf and not
> Apache::Dprof -- the previous is usually too low level.
The code base I'm profiling is very
Raf wrote:
> Apologies for the X-post. It seemed appropriate.
>
> I'm trying to profile a web environment (Apache 1.3.33/Perl 5.8.7/mp 1.29)
> with Apache::SmallProf, however I seem to be getting some odd behaviour
> from DateTime when smallprof is enabled.
>
> We have a module using DateTime.pm
Apologies for the X-post. It seemed appropriate.
I'm trying to profile a web environment (Apache 1.3.33/Perl 5.8.7/mp 1.29)
with Apache::SmallProf, however I seem to be getting some odd behaviour
from DateTime when smallprof is enabled.
We have a module using DateTime.pm, which is used in a CGI
