From: forsyth@plan9.cs.york.ac.uk forsyth@plan9.cs.york.ac.uk
Subject: File Server memory...
Date: Sun, 17 Mar 1996 07:40:47 -0500 [thread overview]
Message-ID: <19960317124047.WqpFfx8Cj6kM9EWY8lyeaWRB6bCDuF4dZjFnb-ILQ9I@z> (raw)
if you are running a file server on a machine with less than (say) 32mbytes,
you might find it worthwhile making the following change to /sys/src/fs/port/main.c:
currently:
conf.nfile = 30000;
i use
if (conf.mem < 32*1024*1024)
conf.nfile = 15000;
else
conf.nfile = 30000;
you could reduce nfile still further if necessary. this reduces the number
of simultaneously open files, but increases the memory available for buffers etc.
next reply other threads:[~1996-03-17 12:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-03-17 12:40 forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
1996-03-17 1:26 Thomas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19960317124047.WqpFfx8Cj6kM9EWY8lyeaWRB6bCDuF4dZjFnb-ILQ9I@z \
--to=forsyth@plan9.cs.york.ac.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).