Re: Response time from perlmonks

We fight a steady ongoing war against server slowdown. As the site scales up we sometimes identify new hot spots in the code and try to resolve them. At times there are definately load issues on the site. One thing that you may want to try is to switch to the .com or .net domains as often they are lower load.

BTW, tye has been doing a lot of work lately on improving caching and other related speed up work, so you can expect sometime in the future that he rolls it all out and hopefully shave some seconds off peak-time fetches.

---
$world=~s/war/peace/g

Comment on Re: Response time from perlmonks

Replies are listed 'Best First'.
Re^2: Response time from perlmonks by xdg (Monsignor) on Aug 18, 2005 at 22:19 UTC
Hmm. I didn't even realize that .com/.net resolved to a different IP. Would it be possible to round-robin the DNS for all three suffixes between the two hosts and automate the load sharing? -xdg Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.	[reply]
Re^3: Response time from perlmonks (round-robin DNS) by tye (Sage) on Aug 19, 2005 at 07:35 UTC
That's how it already is. - tye	[reply]
Re^4: Response time from perlmonks (round-robin DNS) by demerphq (Chancellor) on Aug 19, 2005 at 07:53 UTC
My mistake then. It certainly seemed not to be that way, from the trace log for instance. --- $world=~s/war/peace/g	[reply]