Re: [Catalyst] Catalyst test server response times.
On Thu, Jan 31, 2008 at 10:03:47AM +, Ian Docherty wrote: > Ash Berlin wrote: > > > >On 30 Jan 2008, at 09:51, Andrew Payne wrote: > > > >>On Jan 30, 2008 9:14 AM, Ian Docherty <[EMAIL PROTECTED]> > >>wrote: > >>>It is frequently (but not always) taking 20 seconds or so to display > >>>a > >>>page in my browser > >> > >>The only times I've had this happen, it's been DNS issues -- in my > >>case, dhcpd putting a duff entry in resolv.conf > >> > >>YMMV, but worth checking. > Searching for DNS issues on Catalyst found this link from about 18 > months ago with a > proposed patch to Catalyst::Engine::HTTP.pm to disable reverse DNS if > required. This > would have allowed me to solve this issue but AFAIK this patch was not > applied As I replied at the time: "Proper accessor, make sure it applies cleanly against current subversion trunk, and wait and see what the Engine experts think. Plus a test case would be nice." But he didn't revise the patch, so it didn't get applied. If you want this functionality, please by all means revise the patch accordingly and lob it at [EMAIL PROTECTED] -- Matt S Trout Need help with your Catalyst or DBIx::Class project? Technical Directorhttp://www.shadowcat.co.uk/catalyst/ Shadowcat Systems Ltd. Want a managed development or deployment platform? http://chainsawblues.vox.com/http://www.shadowcat.co.uk/servers/ ___ List: Catalyst@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/
Re: [Catalyst] Catalyst test server response times.
Ash Berlin wrote: On 30 Jan 2008, at 09:51, Andrew Payne wrote: On Jan 30, 2008 9:14 AM, Ian Docherty <[EMAIL PROTECTED]> wrote: It is frequently (but not always) taking 20 seconds or so to display a page in my browser The only times I've had this happen, it's been DNS issues -- in my case, dhcpd putting a duff entry in resolv.conf YMMV, but worth checking. Searching for DNS issues on Catalyst found this link from about 18 months ago with a proposed patch to Catalyst::Engine::HTTP.pm to disable reverse DNS if required. This would have allowed me to solve this issue but AFAIK this patch was not applied http://grokbase.com/profile/id:CFXND-g-bACl4AfTYfKSIP6B7aA91udMOUneLfCbr9E Andrew Also possible is that the Catalyst test server is trying to lookup your reverse DNS. Are you running with or with out debug enabled on the builtin server? ___ List: Catalyst@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/ ___ List: Catalyst@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/
RE: [Catalyst] Catalyst test server response times.
Good write up semi related to the topic. Discusses JavaScript packers and their performance impact as well as security implications. Using some packers may cause false positives on your websites by many security solutions. http://www.secureworks.com/research/threats/thepacker Personally I think the jury is still out on the actual gains of packing JavaScript files aside from the normal whitespace/newline removing techniques. Thanks, -- Ali Mesdaq (CISSP, GIAC-GREM) Security Researcher II Websense Security Labs http://www.WebsenseSecurityLabs.com -- -Original Message- From: Jason Kohles [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 30, 2008 7:49 AM To: The elegant MVC web framework Subject: Re: [Catalyst] Catalyst test server response times. On Jan 30, 2008, at 10:23 AM, Roderick A. Anderson wrote: > Ian Docherty wrote: >> I have moved (back) to using the built in Catalyst server for testing >> purposes. >> It is frequently (but not always) taking 20 seconds or so to display >> a page in my browser even though the timings reported by the Catalyst >> server are about >> 0.2 sec. so I know that >> it is not the Catalyst app that is causing the delay. > > Having read the other postings on this I wonder if you have a large- > ish css or Javascript file being loaded. I've noticed a bit of a > delay when I was trying the Ext2.js examples from the Ext2 site. This delay is related more to the complexity of the javascript than it's size. It's essentially the compile-time penalty of the library in use, ExtJS is one of the bigger ones that I've noticed it on, it can take quite a while for it get loaded/decompressed/setup and ready to go. It's much faster when using a release version rather than a testing version, and there are tools that will let you build custom ExtJS versions with just the features you are actually using included, so you don't have to wait for initialization for features you aren't using. -- Jason Kohles, RHCA RHCDS RHCE [EMAIL PROTECTED] - http://www.jasonkohles.com/ "A witty saying proves nothing." -- Voltaire ___ List: Catalyst@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 ___ List: Catalyst@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/
RE: [Catalyst] Catalyst test server response times.
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:[EMAIL PROTECTED] 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@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 ___ List: Catalyst@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/
Re: [Catalyst] Catalyst test server response times.
Jason Kohles wrote: On Jan 30, 2008, at 10:23 AM, Roderick A. Anderson wrote: Ian Docherty wrote: I have moved (back) to using the built in Catalyst server for testing purposes. It is frequently (but not always) taking 20 seconds or so to display a page in my browser even though the timings reported by the Catalyst server are about 0.2 sec. so I know that it is not the Catalyst app that is causing the delay. Having read the other postings on this I wonder if you have a large-ish css or Javascript file being loaded. I've noticed a bit of a delay when I was trying the Ext2.js examples from the Ext2 site. > This delay is related more to the complexity of the javascript than it's size. It's essentially the compile-time penalty of the library in use, Slap goes the hand to the forehead! Of course I exclaim! ExtJS is one of the bigger ones that I've noticed it on, it can take quite a while for it get loaded/decompressed/setup and ready to go. It's much faster when using a release version rather than a testing version, and there are tools that will let you build custom ExtJS versions with just the features you are actually using included, so you don't have to wait for initialization for features you aren't using. Thanks. I've been looking into ExtJS. This will help a bunch. Rod -- --Jason Kohles, RHCA RHCDS RHCE [EMAIL PROTECTED] - http://www.jasonkohles.com/ "A witty saying proves nothing." -- Voltaire ___ List: Catalyst@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/ ___ List: Catalyst@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/
Re: [Catalyst] Catalyst test server response times.
* On Wed, Jan 30 2008, Ian Docherty wrote: > My bad. Heard and understood. (by the way who is RMS?) Google. It. Regards, Jonathan Rockway ___ List: Catalyst@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/
Re: [Catalyst] Catalyst test server response times.
Matt S Trout wrote: On Wed, Jan 30, 2008 at 10:41:35AM +, Ian Docherty wrote: Ash Berlin wrote: On 30 Jan 2008, at 09:51, Andrew Payne wrote: On Jan 30, 2008 9:14 AM, Ian Docherty <[EMAIL PROTECTED]> wrote: It is frequently (but not always) taking 20 seconds or so to display a page in my browser The only times I've had this happen, it's been DNS issues -- in my case, dhcpd putting a duff entry in resolv.conf YMMV, but worth checking. Andrew Also possible is that the Catalyst test server is trying to lookup your reverse DNS. Are you running with or with out debug enabled on the builtin server? I have also tried running a Catalyst app from another server and it does not have the same delay. I am running with debug enabled. (what difference will that make to my issue?) I have also tried it with the IP address in the URL so that DNS is not (should not be ?) used. hang on... 'reverse' DNS? YUP. turning debug mode off has a *big* difference. so, what is this reverse DNS thingy doing and how can I turn it off but leave the other debug on? http://en.wikipedia.org/wiki/Reverse_DNS_lookup Incidentally, you are not RMS, so I see no reason why you need to send mail to read google for you. Please stop asking trivial, unrelated questions on the list, it's a bit unfair to expect people to do basic research for you - I'd have left it if you only did it occasionally but it's becoming a habit and I'm hearing people bitch about it regularly now. My bad. Heard and understood. (by the way who is RMS?) On this occasion I was really asking how to stop Catalyst from doing the reverse DNS (which I understood, but on reading my posting I can see where you are coming from) whilst leaving debug mode on. Let me say that I thank everyone who has helped on this occasion (and others) and apologise for any unnecessary bandwidth. Regards Ian ___ List: Catalyst@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/
Re: [Catalyst] Catalyst test server response times.
Jason Kohles wrote: On Jan 30, 2008, at 10:23 AM, Roderick A. Anderson wrote: Ian Docherty wrote: I have moved (back) to using the built in Catalyst server for testing purposes. It is frequently (but not always) taking 20 seconds or so to display a page in my browser even though the timings reported by the Catalyst server are about 0.2 sec. so I know that it is not the Catalyst app that is causing the delay. Having read the other postings on this I wonder if you have a large-ish css or Javascript file being loaded. I've noticed a bit of a delay when I was trying the Ext2.js examples from the Ext2 site. This delay is related more to the complexity of the javascript than it's size. It's essentially the compile-time penalty of the library in use, ExtJS is one of the bigger ones that I've noticed it on, it can take quite a while for it get loaded/decompressed/setup and ready to go. It's much faster when using a release version rather than a testing version, and there are tools that will let you build custom ExtJS versions with just the features you are actually using included, so you don't have to wait for initialization for features you aren't using. I am using extjs and realised that this could be an issue but I created a brand new minimal Catalyst application and I saw the same issues. Also I used wget to get the web page, which of course does not execute the javascript. The 15 second long delay is prior to the Catalyst debug information being printed. The actual execution of the various controllers is very quick (sub 0.3 seconds) If I use CATALYST_DEBUG=0 then the problem goes away. Lately, the problem has gone away even without turning debug off. One possibility I am still investigating is that the problem only occurs if two or more developers are running a server at the same time. (jury is still out on this) Regards Ian ___ List: Catalyst@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/
Re: [Catalyst] Catalyst test server response times.
On Wed, Jan 30, 2008 at 10:41:35AM +, Ian Docherty wrote: > Ash Berlin wrote: > > > >On 30 Jan 2008, at 09:51, Andrew Payne wrote: > > > >>On Jan 30, 2008 9:14 AM, Ian Docherty <[EMAIL PROTECTED]> wrote: > >>>It is frequently (but not always) taking 20 seconds or so to display a > >>>page in my browser > >> > >>The only times I've had this happen, it's been DNS issues -- in my > >>case, dhcpd putting a duff entry in resolv.conf > >> > >>YMMV, but worth checking. > >> > >>Andrew > > > >Also possible is that the Catalyst test server is trying to lookup > >your reverse DNS. Are you running with or with out debug enabled on > >the builtin server? > I have also tried running a Catalyst app from another server and it does > not have the same delay. > > I am running with debug enabled. (what difference will that make to my > issue?) > > I have also tried it with the IP address in the URL so that DNS is not > (should not be ?) used. > hang on... 'reverse' DNS? > > YUP. turning debug mode off has a *big* difference. > so, what is this reverse DNS thingy doing and how can I turn it off but > leave the other debug on? http://en.wikipedia.org/wiki/Reverse_DNS_lookup Incidentally, you are not RMS, so I see no reason why you need to send mail to read google for you. Please stop asking trivial, unrelated questions on the list, it's a bit unfair to expect people to do basic research for you - I'd have left it if you only did it occasionally but it's becoming a habit and I'm hearing people bitch about it regularly now. -- Matt S Trout Need help with your Catalyst or DBIx::Class project? Technical Directorhttp://www.shadowcat.co.uk/catalyst/ Shadowcat Systems Ltd. Want a managed development or deployment platform? http://chainsawblues.vox.com/http://www.shadowcat.co.uk/servers/ ___ List: Catalyst@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/
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@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/
Re: [Catalyst] Catalyst test server response times.
On Jan 30, 2008, at 10:23 AM, Roderick A. Anderson wrote: Ian Docherty wrote: I have moved (back) to using the built in Catalyst server for testing purposes. It is frequently (but not always) taking 20 seconds or so to display a page in my browser even though the timings reported by the Catalyst server are about 0.2 sec. so I know that it is not the Catalyst app that is causing the delay. Having read the other postings on this I wonder if you have a large- ish css or Javascript file being loaded. I've noticed a bit of a delay when I was trying the Ext2.js examples from the Ext2 site. This delay is related more to the complexity of the javascript than it's size. It's essentially the compile-time penalty of the library in use, ExtJS is one of the bigger ones that I've noticed it on, it can take quite a while for it get loaded/decompressed/setup and ready to go. It's much faster when using a release version rather than a testing version, and there are tools that will let you build custom ExtJS versions with just the features you are actually using included, so you don't have to wait for initialization for features you aren't using. -- Jason Kohles, RHCA RHCDS RHCE [EMAIL PROTECTED] - http://www.jasonkohles.com/ "A witty saying proves nothing." -- Voltaire ___ List: Catalyst@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/
Re: [Catalyst] Catalyst test server response times.
Ian Docherty wrote: I have moved (back) to using the built in Catalyst server for testing purposes. It is frequently (but not always) taking 20 seconds or so to display a page in my browser even though the timings reported by the Catalyst server are about 0.2 sec. so I know that it is not the Catalyst app that is causing the delay. Having read the other postings on this I wonder if you have a large-ish css or Javascript file being loaded. I've noticed a bit of a delay when I was trying the Ext2.js examples from the Ext2 site. Is apache and cat server using the same files? Could be a file system issue. Rod -- I have also done ping tests to the server and that also is reasonable. What else could be causing the delay? What other checks could I do that would help to diagnose where this huge delay is occurring? How about any static content which is served by C::P::Static? That is not reported by the server, could the delay be in there in some way? (clutching at straws). Regards Ian C. Docherty (icydee) ___ List: Catalyst@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/ ___ List: Catalyst@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/
Re: [Catalyst] Catalyst test server response times.
Peter Edwards wrote: On Jan 30, 2008 9:14 AM, Ian Docherty <[EMAIL PROTECTED]> wrote: It is frequently (but not always) taking 20 seconds or so to display a page in my browser Andrew wrote: The only times I've had this happen, it's been DNS issues -- in my case, dhcpd putting a duff entry in resolv.conf YMMV, but worth checking. YUP. turning debug mode off has a *big* difference. so, what is this reverse DNS thingy doing and how can I turn it off but leave the other debug on? Say your browser PC address is 192.168.1.2 Try typing on your Linux server $ host 192.168.1.2 and see how long it takes to resolve. If it's not almost instant, look at /etc/resolv.conf. If you're using DHCP, that may put an incorrect nameserver entry in there. For example, my router adds itself (192.168.1.1) as the first nameserver although it will time out trying to resolve 192.168.1.2. When that happens, the test server Catalyst::Engine::HTTP::_socket_data() will wait to time out in the call to gethostbyaddr() while serving static files. Try removing any incorrect entries from /etc/resolv.conf so that the 'host' command works quickly and it should be okay. Unfortunately, every DHCP refresh will recreate the file so do "man dhclient-script" and look at making an /etc/dhclient-exit-hooks to rewrite the resolv.conf it creates. 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). Regards, Peter http://perl.dragonstaff.co.uk ___ List: Catalyst@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/ ___ List: Catalyst@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/
RE: [Catalyst] Catalyst test server response times.
>> On Jan 30, 2008 9:14 AM, Ian Docherty <[EMAIL PROTECTED]> wrote: >>> It is frequently (but not always) taking 20 seconds or so to display a >>> page in my browser >> >>Andrew wrote: >> The only times I've had this happen, it's been DNS issues -- in my >> case, dhcpd putting a duff entry in resolv.conf >> >> YMMV, but worth checking. >YUP. turning debug mode off has a *big* difference. >so, what is this reverse DNS thingy doing and how can I turn it off but >leave the other debug on? Say your browser PC address is 192.168.1.2 Try typing on your Linux server $ host 192.168.1.2 and see how long it takes to resolve. If it's not almost instant, look at /etc/resolv.conf. If you're using DHCP, that may put an incorrect nameserver entry in there. For example, my router adds itself (192.168.1.1) as the first nameserver although it will time out trying to resolve 192.168.1.2. When that happens, the test server Catalyst::Engine::HTTP::_socket_data() will wait to time out in the call to gethostbyaddr() while serving static files. Try removing any incorrect entries from /etc/resolv.conf so that the 'host' command works quickly and it should be okay. Unfortunately, every DHCP refresh will recreate the file so do "man dhclient-script" and look at making an /etc/dhclient-exit-hooks to rewrite the resolv.conf it creates. Regards, Peter http://perl.dragonstaff.co.uk ___ List: Catalyst@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/
Re: [Catalyst] Catalyst test server response times.
Ash Berlin wrote: On 30 Jan 2008, at 09:51, Andrew Payne wrote: On Jan 30, 2008 9:14 AM, Ian Docherty <[EMAIL PROTECTED]> wrote: It is frequently (but not always) taking 20 seconds or so to display a page in my browser The only times I've had this happen, it's been DNS issues -- in my case, dhcpd putting a duff entry in resolv.conf YMMV, but worth checking. Andrew Also possible is that the Catalyst test server is trying to lookup your reverse DNS. Are you running with or with out debug enabled on the builtin server? I have also tried running a Catalyst app from another server and it does not have the same delay. I am running with debug enabled. (what difference will that make to my issue?) I have also tried it with the IP address in the URL so that DNS is not (should not be ?) used. hang on... 'reverse' DNS? YUP. turning debug mode off has a *big* difference. so, what is this reverse DNS thingy doing and how can I turn it off but leave the other debug on? ___ List: Catalyst@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/ ___ List: Catalyst@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/
Re: [Catalyst] Catalyst test server response times.
I third DNS issues, the timing of your first mail and your second mail were out of whack. On 30 Jan 2008, at 21:23, Ash Berlin wrote: On 30 Jan 2008, at 09:51, Andrew Payne wrote: On Jan 30, 2008 9:14 AM, Ian Docherty <[EMAIL PROTECTED]> wrote: It is frequently (but not always) taking 20 seconds or so to display a page in my browser The only times I've had this happen, it's been DNS issues -- in my case, dhcpd putting a duff entry in resolv.conf YMMV, but worth checking. Andrew Also possible is that the Catalyst test server is trying to lookup your reverse DNS. Are you running with or with out debug enabled on the builtin server? ___ List: Catalyst@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/ ___ List: Catalyst@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/
Re: [Catalyst] Catalyst test server response times.
Andrew Payne ha scritto: On Jan 30, 2008 9:14 AM, Ian Docherty <[EMAIL PROTECTED]> wrote: It is frequently (but not always) taking 20 seconds or so to display a page in my browser The only times I've had this happen, it's been DNS issues -- in my case, dhcpd putting a duff entry in resolv.conf YMMV, but worth checking. Andrew ___ List: Catalyst@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/ I had similar problems once or twice in the past year, and I remember having played with -k (keep alive flag). If my memory is right, -k was causing delays. I think it's also worth trying with and without -r flag. HTH -- Marcello Romani Responsabile IT Ottotecnica s.r.l. http://www.ottotecnica.com ___ List: Catalyst@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/
Re: [Catalyst] Catalyst test server response times.
On 30 Jan 2008, at 09:51, Andrew Payne wrote: On Jan 30, 2008 9:14 AM, Ian Docherty <[EMAIL PROTECTED]> wrote: It is frequently (but not always) taking 20 seconds or so to display a page in my browser The only times I've had this happen, it's been DNS issues -- in my case, dhcpd putting a duff entry in resolv.conf YMMV, but worth checking. Andrew Also possible is that the Catalyst test server is trying to lookup your reverse DNS. Are you running with or with out debug enabled on the builtin server? ___ List: Catalyst@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/
Re: [Catalyst] Catalyst test server response times.
On Jan 30, 2008 9:14 AM, Ian Docherty <[EMAIL PROTECTED]> wrote: > It is frequently (but not always) taking 20 seconds or so to display a > page in my browser The only times I've had this happen, it's been DNS issues -- in my case, dhcpd putting a duff entry in resolv.conf YMMV, but worth checking. Andrew ___ List: Catalyst@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/
Re: [Catalyst] Catalyst test server response times.
Further information on this. If I make a request to a page served by apache on this server via wget, the response is very quick, typically less than a second during which wget displays the 'HTTP request sent, awaiting response'. If I make a request to a page served by the Catalyst server, wget waits something like 12 seconds or more displaying the 'HTTP request sent, awaiting response...' after which time the catalyst server displays the request (with the 0.2 seconds response time etc.) and returns the document. Furthermore, I have created a new bog-standard Catalyst application and the problem is there also. So the delay seems to be occurring before Catalyst gets to see the request. Ian Docherty wrote: I have moved (back) to using the built in Catalyst server for testing purposes. It is frequently (but not always) taking 20 seconds or so to display a page in my browser even though the timings reported by the Catalyst server are about 0.2 sec. so I know that it is not the Catalyst app that is causing the delay. I have also done ping tests to the server and that also is reasonable. What else could be causing the delay? What other checks could I do that would help to diagnose where this huge delay is occurring? How about any static content which is served by C::P::Static? That is not reported by the server, could the delay be in there in some way? (clutching at straws). Regards Ian C. Docherty (icydee) ___ List: Catalyst@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/ ___ List: Catalyst@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/
