| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 9684.1 | | SMURF::DENHAM | Digital UNIX Kernel | Wed Apr 30 1997 17:47 | 1 |
| Can we see your /etc/sysconfigtab snippets?
|
| 9684.2 | | NNTPD::"[email protected]" | Mark Sowards | Tue May 06 1997 13:18 | 22 |
| Th updated sysconfig.stanza file looks like this.
#
# Modified system parameters
#
ipc:
shm-max = 7020840 # was 4194304
shm-seg = 7020864 # was 32
vm:
ubc-maxpercent = 10 # default was 100%
proc:
autonice = 1 # balance PCU Utilization
All four of these values are rejected on boot. What is strange is that the
new
line method was updated throught this file, but its entry was deleted after
the
next boot. It seems that after it was accepted it was removed.
[Posted by WWW Notes gateway]
|
| 9684.3 | | XIRTLU::schott | Eric R. Schott USG Product Management | Tue May 06 1997 15:00 | 22 |
| >#
># Modified system parameters
>#
>ipc:
> shm-max = 7020840 # was 4194304
> shm-seg = 7020864 # was 32
>vm:
> ubc-maxpercent = 10 # default was 100%
>proc:
> autonice = 1 # balance PCU Utilization
>
>
DON'T DON'T DON'T set ubc-maxpercent to 10....this is a real big
mistake...
This will restrict the size of binaries that can be execed...among
other things...I suggest you don't set it lower than 40%, and
generally leaving it at 100% is fine as the system does adjust to
the needed load.
Normally when you reduce it, you do this in 10% increments.
|
| 9684.4 | Move/remove the commentrs | RHETT::PARKER | | Tue May 06 1997 15:26 | 9 |
|
Good advice in .3! You need to remove the comments after each setting
you want to change. For some reason, sysconfig does not like anything
else on the line. You should place the comments on their own line.
Hth,
Lee
|
| 9684.5 | OK I'll try that | NNTPD::"[email protected]" | Mark sowards | Tue May 06 1997 17:53 | 5 |
| I've been trying to convince my customer that he really wants ubc-maxpercent
at 100%. But He insists. So, since it failed to take there hasn't been a
problem, so far.
I'll try removing the comments.
[Posted by WWW Notes gateway]
|
| 9684.6 | some comments | ALFAM7::GOSEJACOB | | Wed May 07 1997 04:21 | 34 |
| re .2
>shm-seg = 7020864 # was 32
That's a really big number for the maximum number of attached shared memory
segments per process. I guess it will not hurt though. If you are setting
this machine up for Oracle I'd rather set shm-max to whatever is needed to
have the SGA fit into one single segment (if you stay below 2GB that is).
re .3
>DON'T DON'T DON'T set ubc-maxpercent to 10....this is a real big
>mistake...
Well things may look a bit different when the machine is a dedicated
database server. If your database is stored in UFS files you definitely
want to limit the UBC to something like 10% of physical memory. The
data on such a setup will be buffered twice (UBC and SGA in case of
Oracle) and I rather allocate something like 70% of memory to the
database buffer than let it compete with UBC.
Keep in mind that this may be very different when memory is a scarce
resource. But on an 8 GB T'laser 10% is still an awfull lot of memory
for the file cache. And while you are at it make sure to reduce the
metadata cache too.
vfs:
bufcache = 1
Unfortunately you can't get it any lower than 1% with the current
releases of D'Unix.
Just my Oracle/VLM view of things
Martin
|