[Catalyst] Catalyst test server response times.

[Mesdaq, Ali]

Just giving my recommendation for what in my opinion is an ESSENTIAL
tool for any web developer or even power user Firebug for Firefox
https://addons.mozilla.org/en-US/firefox/addon/1843 . Best overall tool
I have found. Lets you debug JavaScript, inspect elements and their dom
properties, lets you modify anything live and see the change, displays
http requests with both post data and returned data, shows response
times for each request item, profiles JavaScript on page, list just goes
on and on. Great for design, debugging, and security.

Thanks,
------------------------------------------
Ali Mesdaq (CISSP, GIAC-GREM)
Security Researcher II
Websense Security Labs
http://www.WebsenseSecurityLabs.com
------------------------------------------

-----Original Message-----
From: Peter Edwards [mailto:peter at dragonstaff.com] 
Sent: Wednesday, January 30, 2008 8:00 AM
To: 'The elegant MVC web framework'
Subject: RE: [Catalyst] Catalyst test server response times.

Hi Ian

>doing a 'host' command on an IP address works instantly and the 
>contents of
the /etc/resolv.conf file
>look to be correct.
>
>Could it be a problem with specific IP addresses rather than with the
nameservers? (I can't cause
>a problem manually with the IP addresses I know the Catalyst app is run
from).

There are a few things you could try to narrow the problem.

1. You're definitely running the server without flags? i.e.
$ perl script/myapp_server.pl
The -k and -d flags slow it down a lot.

2. You've got the latest code?
$ cpan Catalyst::Devel

3. Use the debugger to see where the program is $ perl -d
script/myapp_server.pl

Fire up a request from your browser. If it's slow, press CTRL-C to break
in the debugger and use 'v'iew, '.' and 'T'race to see where you are. It
may seem hit and miss but it's a quick way to see where the program is
at. You can use 'c'ontinue to complete dispatching. Some more notes at
http://catwiki.toeat.com/fromtrac/debugsample

4. Use DProf to profile a couple of requests.
$ PERL5OPT=-d:DProf perl script/myapp_server.pl Do a few requests in
your browser $ dprofpp Will show you which routines are eating up time.

5. Use a browser debugging tool like Fiddler2 in IE
http://www.fiddlertool.com/fiddler/ or Charles in FF
http://www.xk72.com/charles/ if you suspect there's some browser <->
server idiocy going on. See when the request is sent, see when the
header comes back. See how long it takes to get the ancillary .css .js
.jpg files.
That will indicate whether it's a network problem, the server, or simply
slow javascript.

Regards, Peter
http://perl.dragonstaff.co.uk



_______________________________________________
List: Catalyst at lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive:
http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/


 


 Protected by Websense Messaging Security -- www.websense.com