05-23-2013
Thanks Jim.
I had upgraded total RAM from 1Gb to 5Gb and, iirc, load did not decrease (perhaps it even increased). However, there is plenty of free RAM now and it doesn't swap like it used to; ssh seems more responsive. I haven't noticed performance problem really, but we plan to expand oracle database and need to know if hardware can handle it.
7 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi,
I am seeing very high kernel usage and very high load averages on my system (Although we are not loading much data to our database). Here is the output of top...does anyone know what i should be looking at?
Thanks,
Lorraine
last pid: 13144; load averages: 22.32, 19.81, 16.78 ... (4 Replies)
Discussion started by: lorrainenineill
4 Replies
2. Shell Programming and Scripting
hi all
need your help.
I am wrting a script that will load data into the table.
then on another load will append the data into the existing table.
Regards
Ankit (1 Reply)
Discussion started by: ankitgupta
1 Replies
3. UNIX for Dummies Questions & Answers
I know that Sun make s a version of Solaris for Sparc platforms and also an x86 (Intel/AMD) release of Solaris. Can an application that runs on Solaris/Sparc also run on a PC running the x86 release of Solaris? Would a different release be required or any re-compling of the application?
jim (1 Reply)
Discussion started by: stocksj
1 Replies
4. UNIX for Dummies Questions & Answers
Hi Gurus
can I emulate solaris/sparc on virtualbox? Or other emulator to run solaris for sparc in my win7 PC?
regards,
Israel. (9 Replies)
Discussion started by: iga3725
9 Replies
5. Shell Programming and Scripting
`/proc/loadavg` give me three indicators of how much work
the system has done during the last 1, 5 & 15 minutes.
How can i get a list of load averages
that each averaged over the last minute for 10 minutes? (2 Replies)
Discussion started by: navidlog
2 Replies
6. Solaris
Hi Guys,
Could you please tell me how to read this Solaris version:-
Solaris 8 HW 5/03 s28s_hw2wos_06a SPARC
Thanks. (3 Replies)
Discussion started by: manalisharmabe
3 Replies
7. Programming
Here is a useful SSL (HTTPS) application for anyone with a remote Linux server they want to keep an eye on using Blynk and the NodeMCU ESP8266. This little app also works (have tested as well) on the WeMos D1 ESP8266 Arduino board.
The NodeMCU setup could not be easier, just find a... (8 Replies)
Discussion started by: Neo
8 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)