Hi all,
On Thu, Apr 19, 2007 at 05:39:15PM +0200, Alexander Klink wrote:
> own share of problems :-/). Surprisingly enough, we found out that a
> huge amount of time is spent in OpenXPKI::Exception->throw() - while
> generating stack traces using Devel::StackTrace, which we don't even
> use. I've generated a patch for Exception::Class to skip that and
> submitted a bug report, which you can both find at
> http://rt.cpan.org/Ticket/Display.html?id=26489
I've forgot to mention that for the speedup, you also need to patch
OpenXPKI::Exception.pm, just change line 79 from
my $self = $proto->new(%exception_args); to
my $self = $proto->new(%exception_args, 'no_stack_trace' => 1);
As for profiling, I've just added the --foreground option to openxpkictl
start, which does not fork the server away and uses Net::Server::Simple
instead of Net::Server::Fork. This means that you only have one
connection. Make sure to delete stale session cookies on the
webinterface, because if the session can not be continued, the client is
closed which closes the socket which means your server is gone.
To profile using --foreground, just call
perl -d:DProfLB /path/to/openxpkictl start --foreground
Do your thing on the webinterface, press Ctrl-C and run
dprofpp -I -O 50 tmon.out | less
To see the top 50 methods that took the most time.
Best regards,
Alex
--
Dipl.-Math. Alexander Klink | IT-Security Engineer
[EMAIL PROTECTED] | working @ urn:oid:1.3.6.1.4.1.11417
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
OpenXPKI-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openxpki-devel
