Have you looked at whether the CMS is maybe always running its own webserver and Apache is mostly running as a reverse proxy in front of the CMS?
Without seeing the configuration, and knowing more about the CMS in question, and how it actually works/runs, it's hard to give any kind of advice.
In reply to Re: Devel::NYTProf::Apache does not profile our CMS
by Corion
in thread Devel::NYTProf::Apache does not profile our CMS
by feumw
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |