Francisco Reyes wrote:
On Wed, 28 Sep 2005, Eric Anderson wrote:
Keep in mind that 5-STABLE, and 6.x (and -CURRENT) have a max of 256
nfsd's, so if you want to go higher, you have to modify a line in nfsd.c.
So far only a handfull of clients are expected. I am going to start at
10. :-)
Ot
On Wed, 28 Sep 2005, Eric Anderson wrote:
Keep in mind that 5-STABLE, and 6.x (and -CURRENT) have a max of 256 nfsd's,
so if you want to go higher, you have to modify a line in nfsd.c.
So far only a handfull of clients are expected. I am going to start at 10.
:-)
Other than "killall -9 nfsd
Francisco Reyes wrote:
On Fri, 23 Sep 2005, Eric Anderson wrote:
Use the -n flag to nfsd, so in /etc/rc.conf:
nfs_server_flags="-u -t -n 1024"
Working on the nfs server today.
How about the "-r" flag? It is the default. Is it not needed?
The man page says "-r"
Register the NFS service with
On Fri, 23 Sep 2005, Eric Anderson wrote:
Use the -n flag to nfsd, so in /etc/rc.conf:
nfs_server_flags="-u -t -n 1024"
Working on the nfs server today.
How about the "-r" flag? It is the default. Is it not needed?
The man page says "-r"
Register the NFS service with rpcbind(8) without creat
I've found on discussion lists that some people also tested values near
80 or 100. I think I have CPU and RAM to start with a value of 50.
The rsize and wsize values are both 32768.
Thanks in advance,
Mariano.
Eric Anderson wrote:
Mariano Benedettini wrote:
Thanks for all the replies. It's n
Francisco Reyes wrote:
On Fri, 23 Sep 2005, Eric Anderson wrote:
You should also increase the rsize and wsize parameters on the mount
options for better efficiency.
On the server?
On the client (in /etc/fstab or on the command line with -o).
Eric
--
-
On Fri, 23 Sep 2005, Eric Anderson wrote:
You should also increase the rsize and wsize parameters on the mount options
for better efficiency.
On the server?
___
freebsd-performance@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/fr
Mariano Benedettini wrote:
Thanks for all the replies. It's not a HD problem.
On monday I'll increase the number of nfsd processes and the number of
nfsiod on the client, setting both to 50,
I think that the nfs performance will be much better :-)
50 nfsiod's may be a bit overkill, but you sh
Thanks for all the replies. It's not a HD problem.
On monday I'll increase the number of nfsd processes and the number of
nfsiod on the client, setting both to 50,
I think that the nfs performance will be much better :-)
Mariano.
Eric Anderson wrote:
Francisco Reyes wrote:
On Tue, 13 Sep 20
Francisco Reyes wrote:
On Thu, 22 Sep 2005, Eric Anderson wrote:
Also, if it is an NFS server, one should check the cpu times on the
nfsd processes. I've found that many times there aren't enough nfsd
processes to take the load from many clients. Increasing the number
(double it) often help
Hello,
Francisco Reyes wrote,
> On Thu, 22 Sep 2005, Eric Anderson wrote:
>
> >Also, if it is an NFS server, one should check the cpu times on the nfsd
> >processes. I've found that many times there aren't enough nfsd processes
> >to take the load from many clients. Increasing the number (dou
On Thu, 22 Sep 2005, Eric Anderson wrote:
Also, if it is an NFS server, one should check the cpu times on the nfsd
processes. I've found that many times there aren't enough nfsd processes to
take the load from many clients. Increasing the number (double it) often
helps this. The max in 5.3
Francisco Reyes wrote:
On Tue, 13 Sep 2005, mariano benedettini wrote:
91.3% idle
CPU is not the problem. :-)
Mem: 1599M Active, 1704M Inact, 311M Wired, 189M Cache, 112M Buf, 14M
Free
Swap: 2023M Total, 184K Used, 2023M Free
Swap is not the problem.
Do
vmstat 10
Watch the output.
On Tue, 13 Sep 2005, mariano benedettini wrote:
91.3% idle
CPU is not the problem. :-)
Mem: 1599M Active, 1704M Inact, 311M Wired, 189M Cache, 112M Buf, 14M Free
Swap: 2023M Total, 184K Used, 2023M Free
Swap is not the problem.
Do
vmstat 10
Watch the output.
In particular look at the f
I have a mail server running FreeBSD 5.3-RELEASE. It's a dual Xeon with 4gb
of ram.
The server is running Apache (serving Horde) , Postfix, Courier imapd w/SSL,
Amavisd. Also a Postgresql as Horde's storage.
The mail storage is accessed via NFS.
The problem is that it's experiencing a really high l
15 matches
Mail list logo
