01-19-2018
The difference is the speed.
It takes a second to clear the 5GB buffers&cache.
If there is high concurrent I/O it takes a minute.
In the second scenario the filling of 8 GB of RAM happens faster (or much faster).
There is a difference between filling (actual usage) and requesting. Linux serves RAM requests immediately without checking if this is really available, "unlimited overcommitment". For example a java application that claims 25 GB RAM will start, and later crash when it fills it with data.
In contrast, Solaris 10 has "limited overcommitment". For example only commits up to twice the available RAM; a java application that claims 25 GB RAM will only start when there is >13 GB available.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I know that free command displays memory usages however I like to know how the option and the results when I use this command..
PLease respond ASAP
thanx... I am a newbie.. :D (1 Reply)
Discussion started by: LiTo
1 Replies
2. UNIX for Dummies Questions & Answers
Hi there again,
Running Solaris 10 with built-in Java. Seems to compile and run fine.
Problem is: Say I want to see contents of current directory. In a shell, I'd just write "ls" and it outputs the content.
When I write a Java file, I have the following line:
System.out.println("ls");
... (1 Reply)
Discussion started by: EugeneG
1 Replies
3. Shell Programming and Scripting
Hi All
I have something that from the outset seems really trivial but in practice is not quite working.
I have the following code sample in my shell script which illustrates the problem
echo "enter home directory"
read home
mkdir $home/newdir
The user then enters a logical $HOME... (3 Replies)
Discussion started by: kingpin2502
3 Replies
4. UNIX for Dummies Questions & Answers
hi all,
when I run-
wcars1j5#netstat -an | grep 8090
127.0.0.1.8090 *.* 0 0 49152 0 LISTEN
wcars1j5#
1. does this mean that no one is connected to this port?
Regards,
akash (1 Reply)
Discussion started by: akash_mahakode
1 Replies
5. UNIX for Dummies Questions & Answers
I am having trouble figuring this one out.....Is this a 2CPU or a 4CPU v490 with 16GB? I think it is a 2CPU system, looking for confirmation.
$ prtdiag
System Configuration: Sun Microsystems sun4u Sun Fire V490
System clock frequency: 150 MHz
Memory size: 16384 Megabytes
... (1 Reply)
Discussion started by: config_boy
1 Replies
6. UNIX for Advanced & Expert Users
Hello, I need some help to interpret the below output...
What is -/+ buffers/cache?
My understanding is, total RAM is 3986152 Bytes, used RAM is 3950904 bytes.
What is buffers and cached?? Can any one please interpret this output? It would be great help if some one can help me on this?
... (2 Replies)
Discussion started by: govindts
2 Replies
7. Red Hat
Hi Friends,
I am really confused with the output of "free" command on redhat linux.
I can see caching and buffer output on two different areas on the output.
Please let me know whats the difference of these two different outputs.
Here I am pasting the command output of my server.
# free... (3 Replies)
Discussion started by: arumon
3 Replies
8. Solaris
Hi. I wonder what the equal sign in front of the answer means.
I have read man pages and googled but found no answer.
xntpdc -p
=15.5.64.3 15.5.2.51 3 512 377 0.02060 0.057426 0.04965Thanks.
Jan (1 Reply)
Discussion started by: vettec3
1 Replies
9. Shell Programming and Scripting
Hi All,
I have a file with name
Is there a LINUX command that will help me to output the word after the 9th Underscore(_).
ie the output should be DLY in this case.
Can anybody pls help me.
Thanks much in advance,
Freddie (4 Replies)
Discussion started by: dsfreddie
4 Replies
10. Red Hat
I wanted to know the concept of free -m command as there are different rows of Mem, -/+ buffers/cache & Swap in the output. As an example, it is showing 195 as free Mem in my server but 13850 in the free section of the -/+ buffers/cache row. The output needs in depth knowledge of the different... (7 Replies)
Discussion started by: RHCE
7 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)