| Title: | SAP-Notes |
| Moderator: | OSTV03::NAKAYAMA |
| Created: | Mon Nov 09 1992 |
| Last Modified: | Wed Feb 26 1997 |
| Last Successful Update: | Wed Feb 26 1997 |
| Number of topics: | 735 |
| Total number of notes: | 2563 |
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 726.1 | March 1997 | EPS::PATIL | Avinash Patil, DTN:381-6176 | Thu Jan 23 1997 21:06 | 5 |
| 726.2 | USCTR1::ASCHER | Dave Ascher | Fri Jan 24 1997 06:44 | 3 | |
what makes them so sure that the issue is Advfs?
d
| |||||
| 726.3 | OFOSS1::GINGER | Ron Ginger | Fri Jan 24 1997 15:52 | 3 | |
we are worried about the use of cpu0 being much higher that the others.
We see peaks of 70% use on 0 while about 30-40% on all others. We know
advfs does more on cpu0.
| |||||
| 726.4 | single threaded | TROOA::MSCHNEIDER | [email protected] | Fri Jan 24 1997 22:23 | 1 |
As I understand it prior to V4 of UNIX, Advfs was single-threaded. | |||||
| 726.5 | USCTR1::ASCHER | Dave Ascher | Sat Jan 25 1997 17:33 | 6 | |
70% means that there is 30% left. Doesn't sound like a bottleneck
to me.. computes in advfs have to be a whole lot less costly
than the i/o operations... like 1000 to 1.
| |||||
| 726.6 | the Austrian opinion | ATZIS3::WINTERSPERGE | Mon Jan 27 1997 13:19 | 11 | |
Hello !
I agree with Dave, unless the first CPU ain't close to 100% all the
time there should be no bottleneck from the IO load of CPU 0.
Regards
Thomas Wintersperger, Austria
PS: Even without 4.0 you can do some ADVFS tuning with the ADVFS
cache parameter for the Kernel, and have also a look on the # of Oracle
db writer processes !
| |||||
| 726.7 | OFOSS1::GINGER | Ron Ginger | Mon Feb 03 1997 16:04 | 9 | |
Yes, this customer does not TODAY have a bottleneck, but we are trying
to look ahead. We have only their 2 small divisons on line toady, but
in a few months the major divison is to come on line, and it brings
more that tripple our current users. Feeling is if we are running
arounbd 70% on CPU0, and tripple our uses we will have trouble.
We do have info from SAP that v4.0 will be ready in March, and the
customer has just delayed the startup of the new divison until July, so
we may be OK.
| |||||