03-19-2013
Please don't bump posts.
Depends what you mean by full RAM utilized. Lots of big disk operations will churn a lot of your memory into cache, but this memory will still be available for other things at need.
If you just need a big program that eats lots of RAM, prime95 can be used as a memory and CPU stress test.
10 More Discussions You Might Find Interesting
1. SCO
Hi All,
I want to check the CPU Utilization for my SCO UNIX machine. Please suggest some commands to do that.
Thanks,
Am (2 Replies)
Discussion started by: am_yadav
2 Replies
2. Shell Programming and Scripting
What is the command for checking all the processes running on UNIX. Alos can any one share the CPU utilization script to know what are all the processes running and what is the cpu utilization ...
thanks in advance
Perla Mohan (3 Replies)
Discussion started by: perlamohan
3 Replies
3. UNIX for Dummies Questions & Answers
Hi Guys,
How can i check the RAM usage for a particular user on the Linux machine.
What command can be used.
Thanks in advance,
Swapna (1 Reply)
Discussion started by: Swapna173
1 Replies
4. SuSE
If following is the usage of cat /proc/meminfo
MemTotal: 4051304 kB
MemFree: 28544 kB
Buffers: 216848 kB
Cached: 3398628 kB
SwapCached: 0 kB
Active: 455460 kB
Inactive: 3291612 kB
HighTotal: 0 kB
HighFree: 0 kB... (5 Replies)
Discussion started by: bryanabhay
5 Replies
5. Solaris
Any native Solaris commands/scripts to check the utilization of kernel tables/limits in Solaris ? (like equivalent command in HPUX is kcusage) (2 Replies)
Discussion started by: thamurali
2 Replies
6. Solaris
Hi all
I am facing high utilization of my root partition. below is the output of df -h
bash-3.00# df -h
Filesystem size used avail capacity Mounted on
/dev/md/dsk/d10 9.9G 9.4G 406M 96% /
/devices 0K 0K 0K 0% /devices
ctfs ... (13 Replies)
Discussion started by: waqasahsan
13 Replies
7. Hardware
is there a way to skip RAM check on sparc boot before the ok prompt? (2 Replies)
Discussion started by: orange47
2 Replies
8. Solaris
Hello All,
My Server RAM utilization is exceeding 90% and i would like to idnetify the per process RAM utilization..
We are using Solaris 10 10/9 OS release...
Is there any way achieve this ??? Definitely not interested in any of the third party tool but some Solaris command...
... (5 Replies)
Discussion started by: EmbedUX
5 Replies
9. Cybersecurity
We have a system with 4 Xeon Processors each with 10 cores, total 512 GB RAM and 10 TB Hard Drive.
we want to create multiple user accounts with different resource limitations as :
User 1: RAM : 50GB, PROCESSOR: 10 Cores , User folder in home directory of 10GB space.
User 2: RAM :... (5 Replies)
Discussion started by: vaibhavvsk
5 Replies
10. Solaris
is there a way to thoroughly test RAM in Solaris10 (SPARC)?
or is boot test good enough? (5 Replies)
Discussion started by: orange47
5 Replies
RAM(4) Kernel Interfaces Manual RAM(4)
NAME
ram - ram disk driver
SYNOPSIS
/sys/conf/SYSTEM:
NRAM ram_size # RAM disk size (512-byte blocks)
major device number(s):
block: 3
minor device encoding:
must be zero (0)
DESCRIPTION
The ram pseudo-device provides a very fast extended memory store. It's use is intended for file systems like /tmp and applications which
need to access a reasonably large amount of data quickly.
The amount of memory dedicated to the ram device is controlled by the NRAM definition in units of 512-byte blocks. This is also patchable
in the system binary through the variable ram_size (though a patched system would have to be rebooted before any change took effect; see
adb(1)). This makes it easy to test the effects of different ram disk sizes on system performance. It's important to note that any space
given to the ram device is permanently allocated at system boot time. Dedicating too much memory can adversely affect system performance
by forcing the system to swap heavily as in a memory poor environment.
The block file accesses the ram disk via the system's buffering mechanism through a buffer sharing arrangement with the buffer cache. It
may be read and written without regard to physical disk records. There is no `raw' interface since no speed advantage is gained by such an
interface with the ram disk.
DISK SUPPORT
The ram driver does not support pseudo-disks (partitions). The special files refer to the entire `drive' as a single sequentially
addressed file.
A typical use for the ram disk would be to mount /tmp on it. Note that if this arrangement is recorded in /etc/fstab then /etc/rc will
have to be modified slightly to do a mkfs(8) on the ram disk before the standard file system checks are done.
FILES
/dev/ram block file
/dev/MAKEDEV script to create special files
/dev/MAKEDEV.local script to localize special files
SEE ALSO
hk(4), ra(4), rl(4), rk(4), rp(4), rx(4), si(4), xp(4) dtab(5), autoconfig(8)
DIAGNOSTICS
ram: no space. There is not enough memory to allocate the space needed by the ram disk. The ram disk is disabled. Any attempts to access
it will return an error.
ram: not allocated. No memory was allocated to the ram disk and an attempt was made to open it. Either not enough memory was available at
boot time or the kernel variable ram_size was set to zero.
BUGS
The ram driver is only available under 2.11BSD.
3rd Berkeley Distribution Januray 27, 1996 RAM(4)