slow response

[Ishmael Lesolame_1]

I have recently installed HP-UX 10.20 on a D200 with 128MB of RAM and 2x4Gb
disks. It has June '99 Patches and it is running UNIVERSE. All the recommended
parameters for Univers have been configured. The problem is the system is very
very very slow.
When I login, telnet to it, ping or run a command it takes almost forverer to
to give me the prompt/response.

What are the potential problem areas here? How can I resolve this? Any
suggestions out there? [Please feel free to give examples]

Regards

Ishmael

[Bruce Baillie_1]

Do a top to see what process is eating up CPU or if you have GLANCE, check your
IO's.

[Paul Winchcombe_1]

This sounds to me like a name resolution problem.

When you telnet to a unix machine before the login prompt is displayed it does
a gethostbyaddr on you ip address hoping to get your hostname.

Try logging into the D-Class and running
nslookup . Is this slow? It should be instant.

Check /etc/nsswitch.conf --- man switch gives explanation of syntax. The other
file is /etc/resolv.conf used when resolving hostnames using DNS. Try pinging
the nameserver listed in /etc/resolv.conf. If this is slow is there a more
local DNS server that could be used.

Hoepfully some of the above maybe useful

Regards

Paul

[Ishmael Lesolame_1]

Paul, we do not have a DNS hence thereis no resolv.conf file it only uses the
/etc/hosts file. I remember nslookup still slow and returning /etc/hosts!!

Bruce, I have a demo version of glance that I can use, the trouble is I am not
yet farmiliar with it, I am still a novice. I wouldn't know how to
identify/interpret such processes but I think this can be a useful tool.

Guys thanx for your answers though, I will try the top [also shaky here!!] &
and check nsswitch.

[Alan Riggs_1]

Ishmael,
Like Paul I first thought your problem was a name resolution issue. If
nslookup really does go straight to /etc/hosts (No attempt to resolve through
DNS or NIS) then that should not be the case. sar -u 4 10 will give you a
quick look at PU stats. If the idle time is not consistently 0, then you are
not cpu bound. If pinging another IP (not hostname) shows large values for
time, then you have a network slowdown issue (though it may still be local to
the box -- several things can interfere with network transmission rates). If
response is slow but the time values are low, then it points to local process
binding. It is difficult to get into much more detial without having more
details. Feel free to email me if you want to explore the matter more deeply