09-09-2010
Hi,
The implementation of the policy page-space is very complicated to make it real effective.
Sometimes, with some hardware configurations recommended the development of several page-space, one page on each local disk. Then the operations on the page space are actually performed in the area of the disk cache, avoiding a physical write to disk.
For example, a large page swap disk causes the transmission swap-memory block / limit the availability of disk space. IBM does not allow the page to swap more than 20% of disk capacity.
As for the price of IBM introduces newer SSDs. Oracle Database already knows how to use it.
As for page space even remember the versions of AIX 4.x
For example, NFS needs a lot of page space. What if almost all the disk space is available via NFS.
Applications with databases, CATIA want most memory and swap.
The real-time systems would be ideal that the system did not benefit from the swap, but it's just an idea.
Each disk operation is extremely longer time than in memory, cpu very speed, therefore, multi-tasking.
I admit that given by me default values are sometimes inadequate.
Often better to create a second page-space on the second disk than to increase an existing one. Often better to create file page-space then create or increase page-space. You can deactivate file without reboot!!!!
Bye
9 More Discussions You Might Find Interesting
1. AIX
I am working in AIX 4.3.3 , here when we are doing one activity we ran out of space in one mount point, we need to increase the space in that mout point by reducing it in another mount point, can anybody help me out in carrying this activity.
Vipin (3 Replies)
Discussion started by: vipin77
3 Replies
2. UNIX for Dummies Questions & Answers
I know very basic Unix commands s I would really appreacite the assistance of a Unix guru.
I am installing an application on a Sun server, when attempting to install I get an error that says I do not have enough sapce allocated for my install directory. Error says it has 7235m but needs 15360m.... (2 Replies)
Discussion started by: rhack
2 Replies
3. Filesystems, Disks and Memory
I trying to calculate drive space with RAID. I know the equation is:
(n-1)/n * drive capacity
but, when I use that my calculations don't come out when I compare to what I already know exists:
I have 3 - 18.2gb SCSI drives that contain two logical drives C & D.
Using the math, (3-1)/3 * 18.2... (1 Reply)
Discussion started by: JTalbot017
1 Replies
4. AIX
Hi
have IBM aix. unix
my directories are full
when i use
$ df -k
filesystem kbytes used avail capacity mounted on
/dev/root 288880 288880 288880 100% /
/proc 0 0 0 ... (4 Replies)
Discussion started by: raosurya
4 Replies
5. Filesystems, Disks and Memory
Hello,
I have a little problem, I would like to know how to add disk space on an NCR version 4 and above all whether it still contains vdisk space
smp001-4 4.0 3.0
/dev/dsk/vdisk15 3940505 3807833 132672 97% /data
in the dktab :
/dev/dsk/vdisk15 mirror 2 ... (0 Replies)
Discussion started by: magnetic
0 Replies
6. AIX
A check disk space and find /dev/hd4 used 99%. How to increase space. Thank you for advice.
/home/tecsys > df
Filesystem 512-blocks Free %Used Iused %Iused Mounted on
/dev/hd4 1048576 20624 99% 5977 68% /
/dev/hd2 6815744 653032 91% 59194 ... (4 Replies)
Discussion started by: yapcs88
4 Replies
7. Linux
Hi OS Experts
I would like to increase root partition from another partition so that I can save more documents in Home and Desktop. whether it is possible without formating root partition if so please explain
here is o/p of df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda9... (8 Replies)
Discussion started by: Akshay Hegde
8 Replies
8. Solaris
Hi
Please can I have some help in increasing /var in my solaris 10 server.
At the moment the size configured is small and I need to expand it:
df -h
Filesystem size used avail capacity Mounted on
/dev/dsk/c1t0d0s0 869M 510M 307M 63% /
/devices ... (16 Replies)
Discussion started by: fretagi
16 Replies
9. Solaris
Hello All,
I have solaris server running,
uname -a
SunOS host 5.9 Generic_112233-12 sun4u sparc SUNW,Sun-Fire-280R
Filesystem Size Used Available Capacity Mounted on
/dev/md/dsk/d0 9.8G 8.7G 1.0G 90% /
/dev/dsk/c1t1d0s3 4.3G 7.7M 4.2G ... (17 Replies)
Discussion started by: gull05
17 Replies
memx(8) System Manager's Manual memx(8)
NAME
memx - memory exerciser
SYNOPSIS
/usr/field/memx -s [-h] [-ofile] [-ti] [-mj] [-pk]
OPTIONS
The memx options are as follows: Print the help message for the memx command. Disables automatic shared memory testing. Save diagnostic
output in file. Run time in minutes (i). The default is to run until the process receives a CTRL-C or a kill -15 pid command. The memory
size in bytes (j) to be tested by each spawned process. Must be greater than 4095. The default is (total-memory)/20. The number of pro-
cesses to spawn (k). The default is 20. The maximum is also 20.
DESCRIPTION
The memx memory exerciser spawns processes to exercise memory by writing and reading three patterns: 1's and 0's, 0's and 1's, and a random
pattern.
You specify the number of processes to spawn and the size of memory to be tested by each process. If the shmx Shared Memory exerciser is
present, it will be the first process spawned; the remaining processes are standard memory exercisers. The memx exerciser will run until
the process receives a CTRL-C or a kill -15 pid command.
A logfile for you to examine and then remove is created in the current working directory. If there are errors in the logfile, check the
syslog file where the driver and kernel error messages are saved.
RESTRICTIONS
The memx exerciser is restricted by the size of the available swap space. The size of the swap space and the size of internal memory
available determines how many processes can run on the system. For example, If there is 16 Mbytes of swap space and 16 Mbytes of memory,
all of the swap space would be used if all 20 spawned memory exercisers are running. In that event, no new processes would be able to run.
On systems with large amounts of memory and small swap space, you must restrict the number of memory exercisers and/or the size of memory
being tested.
If there is a need to run a system exerciser over an NFS link or on a diskless system there are some restrictions. For exercisers that
need to write into a file system, such as fsx(8), the target file system must be writable by root. Also, the directory in which any of the
exercisers are executed must be writable by root because temporary files are written into the current directory. These latter restrictions
are sometimes difficult to overcome because often NFS file systems are mounted in a way that prevents root from writing into them. Some of
the restrictions may be overcome by copying the exerciser to another directory and then executing it.
You should specify the -s option to disable automatic shared memory testing, which is not supported.
EXAMPLES
The following example tests all of memory by running 20 spawned processes until a CTRL-C or kill -15 pid command is received: %
/usr/field/memx The following example runs 10 spawned processes, memory size 500,000 bytes, for 180 minutes in the background. %
/usr/field/memx -t180 -m500000 -p10 &
SEE ALSO
Commands: cmx(8), diskx(8), fsx(8), shmx(8), tapex(8)
memx(8)