Okay, send it again with the top 10, sorted by -r then. Maybe we can
make more suggestions.
Exclusive Times
%Time ExclSec CumulS #Calls sec/call Csec/c Name
20.5 14.30 15.222 1 14.305 15.222 ELRes::ApacheHandler::handler
0.37 0.261 0.261 99576 0.0000 0.0000 Date::Simple::as_iso
0.22 0.151 0.153 20364 0.0000 0.0000
Params::Validate::_check_regex_fro
m_xs
0.17 0.117 0.117 6580 0.0000 0.0000 Storable::mretrieve
0.13 0.093 0.093 27854 0.0000 0.0000 Date::Simple::_add
0.09 0.065 0.065 2900 0.0000 0.0000 ELRes::Entity::DESTROY
0.08 0.058 0.058 34766 0.0000 0.0000 Date::Simple::DESTROY
0.08 0.054 0.054 41678 0.0000 0.0000 Date::Simple::_compare
0.05 0.035 0.035 12984 0.0000 0.0000 Date::Simple::__ANON__
0.03 0.020 0.020 36 0.0006 0.0005 Template::Context::filter
0.03 0.019 0.019 102 0.0002 0.0002 DBI::common::DESTROY
0.01 0.010 0.010 1 0.0100 0.0100 DynaLoader::bootstrap
0.01 0.010 0.010 1 0.0100 0.0100 ELRes::App::Session::DESTROY
0.01 0.010 -0.000 2 0.0050 -
ELRes::ApacheHandler::trans_handle
0.0000 r
0.01 0.010 0.010 25 0.0004 0.0004 DBD::mysql::db::_login
As I said previously, the handler itself tops everything... I don't know why
it happens... If I use Devel::Timer to profile its parts, I found that this
block takes the most time to run (99.98%):
eval { $app->run };
if ($@) {
$r->log_error("Server error: $@");
$app->send_error(err => $@);
}
But the call should not be included in the handler's ExclSec time, shouldn't
it? The eval doesn't make the call included in the ExclSec time because I've
tested without it and it still use 99.98% of the time...
Wierd eh?
Thanks a lot...
---
Badai Aqrandista
Cheepy (?)
_________________________________________________________________
Sell your car for $9 on carpoint.com.au
http://www.carpoint.com.au/sellyourcar
