performance issue

performance issue data from external webservers

[dareRock]

Hey there,

Just a quick fyi, this is my first post in the Apache forum since i'm realtively new with Apache...

for some reason, my server takes way to long to call and parse a simple rss feed into a webpage.

system specs as follows:
Processor #1 Vendor: GenuineIntel
Processor #1 Name: Intel(R) Pentium(R) 4 CPU 3.00GHz
Processor #1 speed: 3011.089 MHz
Processor #1 cache size: 2048 KB

Processor #2 Vendor: GenuineIntel
Processor #2 Name: Intel(R) Pentium(R) 4 CPU 3.00GHz
Processor #2 speed: 3011.089 MHz
Processor #2 cache size: 2048 KB

Memory: 1024964k/1040064k available (2058k kernel code, 14136k reserved, 772k data, 232k init, 122560k highmem)

it takes literally 45 seconds or more to parse a feed into a page - im using CaRP to do this and a basic html page to run the script.

when i try it on another server - which has similar specs - it happens instantly - as it should.

i can include the IP's where each feed is located in the /etc/hosts file and it works perfectly, but i believe I shouldn't have to do that since it is not required on any other server where i tested the exact same script.

both servers are running
WHM 10.8.0 cPanel 10.8.1-R113
Fedora i686 - WHM X v3.1.0

any advice is appreciated.

if this should have been posted in another forum, my apologies.

thanks all.

[jdMorgan]

> i can include the IP's where each feed is located in the /etc/hosts file and it works perfectly

This sounds like a problem with DNS, then. Your server is choking trying to do a lookup on the feed domain names, unless you enter them into Windows' "local DNS" table in the hosts file. If they are there, then your machine doesn't have to send a DNS request to the network to translate domain to IP address.

Jim

[dareRock]

thanks for the advice jd....so it sounds as though it is a dns resolver issue...basically, the IP i have in my resolver config are slow.....is that correct?

[jdMorgan]

Yes, whatever DNS servers your machine is set up to use are slow, or the connection is faulty, or the domains you specified are not exactly right.

That's just one theory, but it sounds likely based on the difference between using DNS and using the local-hosts-file lookup. Even a 'normally-slow' DNS lookup would only take a second -- not 45 seconds!

I don't really have much DNS expertise, but I think that angle bears some investigation.

Jim

[dareRock]

i agree - the difference in speed should really only be an extra second or two i'd assume - not 45!

ill take your advice and continue the investigation.

thanks for your input on this jim...much appreciated