Hi, I am not a profiling expert and ceased to be an Apache expert about 15 years ago, but I'm not sure your approach will work, depending on where in your stack you are calling it.

From the doc on threaded/multiprocess programs:

Devel::NYTProf is not currently thread safe or multiplicity safe. If you'd be interested in helping to fix that then please get in touch with us. Meanwhile, profiling is disabled when a thread is created, and NYTProf tries to ignore any activity from perl interpreters other than the first one that loaded it.

... but on the other hand, the doc for `endatexit` says:

Sets the PERL_EXIT_DESTRUCT_END flag in the PL_exit_flags of the perl interpreter. This makes perl run END blocks in perl_destruct() instead of perl_run() which may help in cases, like Apache, where perl is embedded but perl_run() isn't called.

I don't know why your output files are disappearing, but note that the default output location for the files is the current directory.

Hope this helps!

I once had a Teamviewer Session with someone who explained me how this works. Unfortunately bad habits lead me to not documenting it. I haven't placed any Flags/Markers in my Scripts to start/stop profiling. I want to profile a CMS and the last time we did this by starting the Webserver, doing a single click and stopping webserver after. With stopping the profiling ends aswell. I don't want to dive to deep. The last time I got a hint that 80% loading time was SQL so I could took a more detailed look on it. I have to see what I can do. Anyway, thank you, I will probably take a look on the docs again if I can't find an easy quick way to rudimentory profile the problems.

probably a nytprof.out.XXX file for each CGI script spanwed with a PID of XXX? Try a different output dir, files in /tmp are in the death row. Otherwise do your profiling or copy the files elsewhere while the beast is still alive (but hypernating).

Oftentimes you just can't beat the beast

(friday night bonus: unless you use a steely knife).

Edit: these may be helpful: Using Devel::NYTProf with CGI::Application, https://wiki.koha-community.org/wiki/Profiling_with_Devel::NYTProf

bw, bliako

I thought about changing the output directory aswell on Friday, and so did I. Now I have the nytprod.out.xxx files on a different spot and they won't dissappear when I stop the webserver. Now I have to see how/what can I do with them. Unfortunately nytprofhtml still doesn't work with those files:

Reading nytprof.out
Failed to open input 'nytprof.out': No such file or directory at /usr/
+local/lib64/perl5/Devel/NYTProf/Data.pm line 87.
[download]

What is the actual invocation you are using? If the files look like nytprof.out.123 then you need to use the -f flag, e.g. nytprofhtml -f nytprof.out.123 . More details are at nytprofhtml.

It is probably also worth looking at the Apache specific docs in Devel::NYTProf::Apache as it seems not to have been mentioned thus far. (I have never used it, though).

There is also nytprofmerge if you have multiple output files and want to combine the results.