Hi admins,
I have a DS10 (EV6_at_463MHz) running Tru64 v4.0F.
There's 256MB phys. memory
750MB swap has been allocated. The swap mechanism is set to eager.
I saw a strange thing: atsar -r shows memory/swap usage:
# atsar -r
phy ubc free % swap free %
13:30:00 256.0M 145.4M 1.0M ( 0) 750.0M 590.9M ( 78) eager
13:35:00 256.0M 146.7M 1.4M ( 0) 750.0M 593.5M ( 79) eager
The system is almost out of phys. memory.
When in eager mode, the system reserves swapspace for each (modifyable) page
in memory, right? So, when there's only 1M left of the physical memory, why
is swap still at 80% available?
Why doesn't the system seem to start swapping when now I'm out of phys.
memory?
(vmstat/swapon show the same values as atsar)
btw: this is the vmstat output...
procs memory pages intr cpu
r w u act free wire fault cow zero react pin pout in sy cs us sy
id
2 98 32 24K 140 6424 52M 12M 15M 2M 11M 151K 11 358 325 0 1
98
3 97 32 24K 128 6424 0 0 0 0 0 0 17 2K 344 5 1
94
2 98 32 24K 128 6424 252 13 218 0 12 0 13 9K 354 11 3
86
2 98 32 24K 128 6424 75 0 74 0 0 0 3 251 311 0 1
99
2 98 32 24K 128 6424 74 0 74 0 0 0 5 298 340 0 1
99
2 98 32 24K 128 6427 0 0 0 0 0 0 8 1K 327 7 1
91
2 98 32 24K 128 6427 151 0 150 0 0 0 3 249 317 0 1
99
any hints, ideas?
should swap be set to lazy?
Tia,
Alex Harkema
Received on Thu Apr 12 2001 - 11:51:20 NZST