Hi there,
When I run top on my machine it says I have 497M swap space in use, and 380M swap space free,
but I have only allocated 512M swap space to the machine!!!!
Does anyone know how swap used is calculated in the top command?
Thanks... (1 Reply)
Hi there,
I´m trying to get the information of vmstat & top in two different logfiles.
That not that difficult.
vmstat 30 >> myfile.log
top >> myfile2.log
But I also like to include a timestamp every 30 sec to be sure from what date the logs are.
For the Top command I were able to... (2 Replies)
Hi
I have checked the output of top command in which there is a difference shown between the swap of top command for a process with total swap memory usage of the top command.
Swap usage of process is higher than the total swap memory usage.
top - 18:28:21 up 7:13, 5 users, load... (2 Replies)
Hi all,
I have a server running an Oracle database that is part of a Solaris M5000 container. Presumably this is referred to as a zone within a cluster, not sure if I get the terminology right.
Anyway, a third-party manages the zone and unfortunately is not "helpful/friendly" to assist me on... (1 Reply)
Hi,
OS = Solaris 5.10
I need some guidance on interpreting vmstat to confirm whether my server is swapping or not. Can anyone please advise whether the column to check on the vmstat output is the pi column, does higher pi values means the server is swapping or am having swapping issues?
... (1 Reply)
Hi all,
OS = Solaris 5.10
Without using top, can anyone please advise how to get the current swap space that is assigned to a sub-zone that is part of the Solaris zone? Some of the servers does not have the top command and I do not have access to run zone level commands either like zonecfg... (3 Replies)
Hi,
i have done a blunder here, i increased the swap space on Xen5.6 server machine using below steps :-
1056 dd if=/dev/zero of=/root/myswapfile bs=1M count=1024
1057 ls -l /root/myswapfile
1058 chmod 600 /root/myswapfile
1059 mkswap /root/myswapfile
1060 swapon /root/myswapfile
... (1 Reply)
RHEL 5.4
Our Linux machine seemed to be running slow. So, I ran the top and vmstat commands.
Question1.
I can see the process 11517 consuming 100% CPU . But that just means that this process totally utilizes one of the cores in a mult-core CPU. Right ? This machine apparently has two... (2 Replies)
Discussion started by: kraljic
2 Replies
LEARN ABOUT ULTRIX
memx
memx(8) System Manager's Manual memx(8)Name
memx - memory exerciser
Syntax
/usr/field/memx [ -h ] [ -s ] [ -ofile ] [ -ti ] [ -mj ] [ -pk ]
Description
The 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 pat-
tern.
You specify the number of processes to spawn and the size of memory to be tested by each process. The first process is a shared memory
exerciser, the remaining are standard memory exercisers. The exerciser will run until the process receives a or a kill -15 pid.
A logfile is made in for you to examine and then remove. If there are errors in the logfile, check the file, where the driver and kernel
error messages are saved.
Options
The options are:
-h Print the help message for the command.
-s Disable shared memory testing.
-ofile Save diagnostic output in file.
-ti Run time in minutes (i). The default is to run until the process receives a or a kill -15 pid.
-mj The memory size in bytes (j) to be tested by each spawned process. Must be greater than 4095. The default is (total-memory)/20.
-pk The number of processes to spawn (k). The default is 20. The maximum is also 20.
Restrictions
The exerciser is restricted by the size of swap space available. The size of the swap space and the size of internal memory available will
determine how many processes can run on the system. For example, If there were 16Mbytes of swap space and 16Mbytes of memory, all of the
swap space would be used if all 20 spawned memory exercisers were running. In that event, no new processes would be able to run. On sys-
tems 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 the target file system must be writable by root. Also the directory, in which any of the exer-
cisers 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.
Examples
The following example tests all of memory by running 20 spawned processes until a or kill -15 pid 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
Guide to System Exercisers
memx(8)