Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the devel-nytprof CPAN distribution.

Report information
The Basics
Id: 86277
Status: resolved
Priority: 0/
Queue: devel-nytprof

Owner: Nobody in particular
Requestors: zefram [...]

Bug Information
Severity: Wishlist
Broken in: (no value)
Fixed in: (no value)

Subject: wishlist: repeated saving
Date: Thu, 20 Jun 2013 12:20:37 +0100
To: bug-Devel-NYTProf [...]
From: Zefram <zefram [...]>
Download (untitled) / with headers
text/plain 1.5k
Separating this out from the Apache2::SizeLimit issue... It ought to be possible to save profiling data without stopping collection of profiling data, and it ought to be possible to save more than once in one process. Each save operation saves the data that has been collected since the previous save. Each save probably needs to go to a separate file; you'll need nytprofmerge to combine them into a single file for report generation. The purpose of multiple saving is to get useful profiling data out of a process that may die unpredictably in a way that D:NYTP doesn't catch. This comes up a lot with Apache, where things like Apache2::SizeLimit terminate a worker process after some request has been handled, with no simple way to predict which request will do it. With multiple saving, you can set up a PerlCleanupHandler, running after each request, that saves data without stopping profiling. This means you can always pick up data covering every request processed so far, regardless of the current state of child processes. You then lose very little if you fail to trap child termination. Processes can be killed uncleanly and you've still got profiling data from everything they did except what they were working on at the time of killing. You pointed at the existing ability to start and stop data collection repeatedly at runtime. That doesn't do what I'm after, because it doesn't save the data collected so far. Currently, saving profile data once means that no more data can be saved from that process. -zefram
Download (untitled) / with headers
text/plain 275b
You can already call finish_profile(), which will write the accumulated sub profiler data and other end-of-run data. I believe that calling enable_profile() after that will start a new profile. So I think the foundations you need are already there. Or am I missing something?
Subject: Re: [ #86277] wishlist: repeated saving
Date: Thu, 20 Jun 2013 17:45:17 +0100
To: Tim_Bunce via RT <bug-devel-nytprof [...]>
From: Zefram <zefram [...]>
Download (untitled) / with headers
text/plain 234b
Tim_Bunce via RT wrote: Show quoted text
>I believe that calling enable_profile() after that will start a new profile.
Ah, looks like it does. I got confused by the coupling between control of data collection and control of writing, sorry. -zefram
Download (untitled) / with headers
text/plain 106b
Great. I'll happily take a doc patch to clarify things. p.s. I've just uploaded Devel-NYTProf-5.04.tar.gz

This service is sponsored and maintained by Best Practical Solutions and runs on infrastructure.

Please report any issues with to