10-22-2013
Quote:
Originally Posted by
lupin..the..3rd
only certain specilized applications are even capable of doing GPGPU work. [...] A 16 core CPU on the desktop is a waste, unless you're doing a massive amount of code compiling, or some kind of specialized scientific work.
That is exactly the idea. We need raw unadulterated computing power all coming from a single piece of retail circuitry. A RAM only computer that will run data intensive simulations for years on end, with daily monitoring of results and monthly data uploads.
We have already developed expertise in multi-threaded C++ and are looking to foray into CUDA and pyCUDA. About 40% of our computers already run in RAM only with a USB stick for startup and data.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi have just built a new sunfire 280r with solaris 9 and i Have 2 questions
1) where can i view some information that will tell me for definate that the 2*900 mhz processors are both being used, i tried using "top" but it doesnt tell me for sure that both processors are churning away together
... (3 Replies)
Discussion started by: hcclnoodles
3 Replies
2. UNIX for Dummies Questions & Answers
hi,
i want to know cpu utilizatiion per process per cpu..for single processor also if multicore in linux ..to use these values in shell script to kill processes exceeding cpu utilization.ps (pcpu) command does not give exact values..top does not give persistant values..psstat,vmstat..does njot... (3 Replies)
Discussion started by: pankajd
3 Replies
3. Solaris
Hello Friends,
On one of my Solaris 10 box, CPU usage shows 100% using "sar", "vmstat". However, it has 4 CPUs and prstat and glance are not showing enough processes to justify high CPU utilization.
=========================================================================
$ prstat -a
... (4 Replies)
Discussion started by: mahive
4 Replies
4. Solaris
Can anyone tell me difference between cpu-shares vs cpu-cap in solaris & how FSS will work with cpu-caps ? (9 Replies)
Discussion started by: fugitive
9 Replies
5. Hardware
For the selection of motherboards, is there any naming convention in the type numbers? There is usually a brand name and sometimes a version name, but more essential details like form factor, SATA speed and maximum amount of RAM is never given. Is there a reason for that? Is there any background... (2 Replies)
Discussion started by: figaro
2 Replies
6. UNIX Benchmarks
p520's prtconf ..two internal drives 10K RPMs 140G, 2 dual core 1.5 GHz processors, 8 Gig of RAM, running AIX 7.1, with the newest gcc compiler
The numbers don't make sense,
Can someone comment ??
BYTE UNIX Benchmarks (Version 3.11)
System -- AIX p520 1 7 00CD5D0C4C00
Start... (2 Replies)
Discussion started by: ppchu99
2 Replies
7. Hardware
Hi, I am experiencing troubles with dual monitors in fedora 16. During boot time both monitors are working, but when system starts one monitor automatically shut down. It happend out of the blue. Some time before when I updated system this happend but then I booted older kernel release and... (0 Replies)
Discussion started by: wakatana
0 Replies
8. UNIX for Dummies Questions & Answers
We have a single threaded application which is restricted by CPU usage even though there are multiple CPUs on the server, hence leading to significant performance issues. Is it possible to merge / combine multiple CPUs at OS level so it appear as a single CPU for the application? (6 Replies)
Discussion started by: Dissa
6 Replies
9. Linux
Hey all,
So, I want to build a tablet that will run a standard 32-bit version of Linux.
The reason for this is I need to run my application on a very bright screen to use outdoors. I don't want to spend the time porting all of the code to use on an ARM tablet. The application works flawlessly... (2 Replies)
Discussion started by: fedora18
2 Replies
10. UNIX for Beginners Questions & Answers
I read that Entitlement CPU should be set to max 75% compare to Virtual CPU. May I know the reason.
I have set the Entitlement CPU = Virtual CPU on AIX . It works fine .
Can you help to understand. (1 Reply)
Discussion started by: gabhanes
1 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)