Hi,
You have two separate issues:
1) memlog
I noticed that the errors were detected within the first hour
after bootup...and memlogp runs once an hour. I.e., the two
pages had errors essentially immediately after bootup.
I'd get your hardware maintainer to fix that memory.
With the new page-deallocation scheme, you can't tell how
bad the memory is...is it having one correctable error an
hour, or one a second? Hence, the only real clue we have is
that it was just after bootup (i.e., pretty quickly), so I'd
suggest replacing it. The other alternative is to clear the
memory log, and reboot ... and see if the same two pages
get marked bad within the first 2 or 3 hours after bootup.
If they do, then the problem is repeatable. If they don't,
then maybe it was caused by cosmic rays.
However, this isn't affecting performance.
2) performance
> We are also trying to determine if we have enough memory. According to
> HP Response Center we do, but we continue to have page fault rates above
> the normal recommendations (above 50.00/sec) and have users and
> processes waiting on memory. We currently have 896 mb of physical
> memory. We are on operating system 5.5.7 and have 250 users on this
> box.
a) what's the speedometer show during times when you think
the system is slow?
http://www.allegro.com/papers/dump.html#Speedometer
for how to see/read it.
If it's less than, say, 70% busy, then you're waiting for
something (disk I/O or locks)
If it's more than 70% busy, then you've run out of CPU.
Note that adding CPUs isn't always a solution, because in
some cases the OS might not be able to utilize extra CPUs
efficiently. HP's made some performance improvements in
that area, but at the cost of slowdowns in other areas.
b) what's RAMUSAGE (free tool) show for how memory is being used?
http://www.allegro.com/software/hp3000/allegro.html#RAMUSAGE
Stan Sieler [log in to unmask]
www.allegro.com/sieler/wanted/index.html www.allegro.com/sieler
|
