03-05-2002
You might try increasing ncsize in /etc/system try 5000 as well as doubling that for ufs_ninode (10000).
It sounds like you have a larger problem though. Solaris out of the box is tuned for workstation use, and it sounds like you have a server here. I'd look at increasing maxpgio and slowscan. Your hardware is definitly capable of handling the loads youre subjecting it to....what you have is a kernel tuning problem.
7 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi,
1-in vmstat commande line, in reply, which column is the more important to look and verify if server is very slow ?
2-how can I see how many sessions are opened with the same login ?
Many thanks before. (2 Replies)
Discussion started by: big123456
2 Replies
2. UNIX for Advanced & Expert Users
Hi,
I have this on a AIX UNIX machine :
ps aux| head -20
USER PID %CPU %MEM SZ RSS TTY STAT STIME TIME COMMAND
root 516 23.7 0.0 12 15808 - A 19:38:15 903:13 wait
root 774 23.7 0.0 12 15808 - A 19:38:15 902:13 wait
root 1290 23.6 0.0 ... (2 Replies)
Discussion started by: big123456
2 Replies
3. UNIX for Advanced & Expert Users
i want to determine I/O performance of an
executable,
but iostat dont give correct results because
the disk that i am writing to and reading from,
are not physical disk of the host machine,
instead of these local disks we are using
a network storage.
is there any standard way in unix to get... (2 Replies)
Discussion started by: gfhgfnhhn
2 Replies
4. UNIX for Advanced & Expert Users
Hi,
on a linux server I have the following :
vmstat 2 10
procs memory swap io system cpu
r b w swpd free buff cache si so bi bo in cs us sy id
0 4 0 675236 39836 206060 1617660 3 3 3 6 8 7 1 1 ... (1 Reply)
Discussion started by: big123456
1 Replies
5. News, Links, Events and Announcements
About 4 years ago I wrote this tool inspired by Rob Urban's collect tool for DEC's Tru64 Unix. What makes this tool as different as collect was in its day is its ability to run at a low overhead and collect tons of stuff. I've expanded the general concept and even include data not available in... (0 Replies)
Discussion started by: MarkSeger
0 Replies
6. Solaris
Hi all,
I have two storadge 3510 Fc .. with 12 disks 146Gb ..total 1752Gb each storadge. I need to use about 1.4 Tb of it. and want RAID1 ..
I need 13 mount points ..
So question:
for best performance and redundjancy how I must do it.
create 13 logical drives on each stordge with same size... (1 Reply)
Discussion started by: samar
1 Replies
7. UNIX for Dummies Questions & Answers
hi I am having a performance issue with the following requirement
i have to create a permutation and combination on a set of three files
such that each record in each file is picked and the output is redirected in
a specific format but it is taking around 70 odd hours to prepare a
combination... (7 Replies)
Discussion started by: mad_man12
7 Replies
LEARN ABOUT DEBIAN
cfsndserv
CFSNDSERV(6) cfsndserv CFSNDSERV(6)
NAME
cfsndserv - crossfire client sound server
DESCRIPTION
getzone adjusts and mixes sounds before playing them
USAGE
getzone none - started automatically by crossfire client
CONFIGURATION OPTIONS
~/.crossfire/sndconfig can contain the following options:
stereo
1 means stereo sound, 0 - mono
bits
bitrate of generated sound - 8 or 16
signed
if we should sent signed data to the soundcard. 1 means yes.
frequency
speed of playing data. This should be 11025, or sound pitch will change
buffers
how many buffers to allocate
buflen
how big the buffers should be. buffers*buflen shouldn't be smaller than the longest sound to be played.
simultaneously
home many sound can be played at the same time. When this setting is bigger, each sound volume will decrease.
HOW DOES IT WORK
?
The sound server gets information about sounds to be played on standard input.
The information is a line: <sound number> <sound type> <relative x> <relative y> All those numbers are hex. The file ~/.crossfire/sounds
contains description of sound numbers and types. For example:
3 0 5 0
Means that normal sound SOUND_FUMBLE spell should be played as it's source was5 units to the right of player.
Sounds are mixed in special buffers, which are in fact one buffer, which should be big enough for the biggest sound to be played.
The buffers, if contain anything, are sent one by one to the sound device. Each buffer is cleaned after playing.
Sounds data is multiplied by some ratio (<1) evaluated from it's position and volume and added to the buffers, starting from the next after
the one being played.
So bigger buffer means bigger delay, before th sound is actually played, but the smaller buffer is, the bigger is possibility, we won't
succeed filling the next buffer, before last is played.
SEE ALSO
crossfire(1)
http://crossfire.real-time.com
AUTHOR
Jaakko Niemi put this page together for Debian packages by cutting
and pasting from README file of crossfire-client.
3rd Berkeley Distribution 2002-02-23 CFSNDSERV(6)