Re: help analyzing low system(with sar/vmstat/u386mon/sarcheck data)
- From: yannanqi@xxxxxxx
- Date: Sat, 5 Apr 2008 02:14:25 -0700 (PDT)
Sorry for my absence of these days,I'm on a national holiday:) and
your rich knowledge and patience defeat me.... Thanks again.
(1)Bela Lubkin wrote:
Bill Campbell wrote:
Does the system exhibit this type of performance on the console?
If it doesn't, the problem is most likely network related.
I have seen major problems with NICs which show high numbers of
errors on incoming and outgoing packets. On Linux systems the
ifconfig command shows the error history, but SCO's doesn't, at
least not on the OSR 5.0.6a systems we have here.
netstat -i; ndstat -l
Bela<
Because the application needs operator ID and password to login, I
can't test it on the console. But I'll try to do it later and feedback
the result to you. The NIC should be ok, because the old application
works fine. The following is the result of "netstat & ndstat":
# netstat -i
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs
Coll
net1 1500 142.70 zjyw-38 8460437 0 7113058 0
469448
lo0 8232 loopback localhost 2467255 0 2467255 0
0
atl0* 8232 none none No Statistics Available
# ndstat
Device MAC address in use Factory MAC Address
------ ------------------ -------------------
/dev/net1 00:15:60:a5:ac:80 00:15:60:a5:ac:80
Multicast address table
-----------------------
01:00:5e:00:00:01
FRAMES
Unicast Multicast Broadcast Error Octets Queue Length
---------- --------- --------- ------ ----------- ------------
In: 7943453 0 517623 0 613619190 0
Out: 7113607 0 1 0 500415540 0
# ndstat -l
Device MAC address in use Factory MAC Address
------ ------------------ -------------------
/dev/net1 00:15:60:a5:ac:80 00:15:60:a5:ac:80
Multicast address table
-----------------------
01:00:5e:00:00:01
FRAMES
Unicast Multicast Broadcast Error Octets Queue Length
---------- --------- --------- ------ ----------- ------------
In: 7943990 0 517715 0 613689653 0
Out: 7114102 0 1 0 500466929 0
DLPI Module Info: 2 SAPs open, 18 SAPs maximum
5281 frames received destined for an unbound SAP
MAC Driver Info: Media_type: Ethernet
Min_SDU: 14, Max_SDU: 1514, Address length: 6
Interface speed: 10 Mbits/sec
DLPI Restarts Info: Last queue size: 0
Last send time: 6080505
Restart in progress: 0
Number of restarts: 0
Interface Version: MDI 100
ETHERNET SPECIFIC STATISTICS
Collision Table - The number of frames successfully transmitted,
but involved in at least one collision:
Frames Frames
------- -------
1 collision 229269 9 collisions 125
2 collisions 55519 10 collisions 19
3 collisions 15181 11 collisions 2
4 collisions 9432 12 collisions 0
5 collisions 6231 13 collisions 0
6 collisions 1748 14 collisions 0
7 collisions 248 15 collisions 0
8 collisions 151 16 collisions 0
Bad Alignment 0 Number of frames received that
were
not an integral number of octets
FCS Errors 0 Number of frames received that
did
not pass the Frame Check Sequence
SQE Test Errors 0 Number of Signal Quality Error
Test
signals that were detected by the
adapter
Deferred Transmissions 118929 Number of frames delayed on the
first transmission attempt
because
the media was busy
Late Collisions 0 Number of times a collision was
detected later than 512 bits into
the transmitted frame
Excessive Collisions 0 Number of frames dropped on
transmission
because of excessive collisions
Internal MAC Transmit 0 Number of frames dropped on
transmission
Errors because of errors not covered
above
Carrier Sense Errors 0 Number of times that the carrier
sense
condition was lost when
attempting to
send a frame that was deferred
for an
excessive amount of time
Frame Too Long 0 Number of frames dropped on
reception
because they were larger than the
maximum Ethernet frame size
Internal MAC Receive 0 Number of frames dropped on
reception
Errors because of errors not covered
above
Spurious Interrupts 0 Number of times the adapter
interrupted
the system for an unknown reason
No STREAMS Buffers 0 Number of frames dropped on
reception
because no STREAMS buffers were
available
Underruns/Overruns 0 Number of times the transfer of
data to or from the frame buffer
did not complete successfully
Device Timeouts 0 Number of times the adapter
failed to
respond to a request from the
driver
#
(2)The filesystems are mostly free,so this shouldn't be the problem:
# dfspace
/ : Disk space: 7434.21 MB of 8927.00 MB available
(83.28%).
/stand : Disk space: 2.41 MB of 14.99 MB available (16.12%).
/serv : Disk space: 27516.99 MB of 29998.61 MB available
(91.73%).
/servbak : Disk space: 28590.46 MB of 29999.01 MB available
(95.30%).
(3)
Much more likely: you've got dirty buffer cache storms. You've given
the system 450MB of buffer cache. A process that was writing very
quickly to an already allocated file could dirty tens of megabytes in a
few seconds. Those blocks would stay in cache until bdflush was run,
then they would all try to write to disk at the same time, busying out
the disk for a long time.
To mitigate this, change BDFLUSHR to 1 (run bdflush as often as
possible, once a second) and NAUTOUP to 2 (flush buffers that are no
more than 2 seconds old). This costs a bit of extra CPU, but your
system has plenty to spare.
This shouldn't be the point. Because the application generates little
writes, totally about 20M one day.
(4)
I seem to remember that one of the OSR507 patches also improved some
buffer cache handling. With your 506, the system might actually run
_faster_ with a much smaller buffer cache. You should test it with a
sharp reduction, e.g. NBUF=50000; revert back to 450000 if it doesn't
help.
I'll test it and feedback the result as soon as possible.
(5)
Because of the buffer cache & filesystem space allocation improvements,
this system would probably be a lot happier under OSR507 + MP5. (Or it
might make no difference... can't really tell without trying.)
I have no method... Because the software supplier says their
application only support OSR506 and OSR505.
.
- Follow-Ups:
- Re: help analyzing low system(with sar/vmstat/u386mon/sarcheck data)
- From: James_Szabadics
- Re: help analyzing low system(with sar/vmstat/u386mon/sarcheck data)
- From: Bela Lubkin
- Re: help analyzing low system(with sar/vmstat/u386mon/sarcheck data)
- References:
- help analyzing low system(with sar/vmstat/u386mon/sarcheck data)
- From: yannanqi
- Re: help analyzing low system(with sar/vmstat/u386mon/sarcheck data)
- From: Bill Campbell
- Re: help analyzing low system(with sar/vmstat/u386mon/sarcheck data)
- From: Bela Lubkin
- help analyzing low system(with sar/vmstat/u386mon/sarcheck data)
- Prev by Date: Re: user permission problems
- Next by Date: Re: help analyzing low system(with sar/vmstat/u386mon/sarcheck data)
- Previous by thread: Re: help analyzing low system(with sar/vmstat/u386mon/sarcheck data)
- Next by thread: Re: help analyzing low system(with sar/vmstat/u386mon/sarcheck data)
- Index(es):
Relevant Pages
|