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 wrote:
On Mon, 5 Sep 2005, Chuck Swiger wrote:
Small writes are pretty much the worst-case scenario for RAID-5,
Such as mail servers?
How about for a DB server which is mostly read only?
normal to see a very significant performance drop-- by up to an order
of magnitude-- from the
Francisco Reyes wrote:
On Fri, 23 Sep 2005, Joseph Koshy wrote:
Is there a way to find out which program(s) are causing
the I/O?
ktrace(8); you can use it to trace all descendants of 'init'.
Looking at the man page it's non-obvious how to use it (to me).
Specially it seems one needs to
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
Hello,
Francisco Reyes wrote,
> On Fri, 23 Sep 2005, Joseph Koshy wrote:
>
> >>Is there a way to find out which program(s) are causing the I/O?
> >
> >ktrace(8); you can use it to trace all descendants of 'init'.
>
> Looking at the man page it's non-obvious how to use it (to me).
>
>
> Special
On Mon, 5 Sep 2005, Chuck Swiger wrote:
Small writes are pretty much the worst-case scenario for RAID-5,
Such as mail servers?
How about for a DB server which is mostly read only?
normal to see a very significant performance drop-- by up to an order of
magnitude-- from the performance of a b
On Fri, 23 Sep 2005, Joseph Koshy wrote:
Is there a way to find out which program(s) are causing
the I/O?
ktrace(8); you can use it to trace all descendants of 'init'.
Looking at the man page it's non-obvious how to use it (to me).
Specially it seems one needs to indicate a pid or a comman
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
Am 23.09.2005 um 05:05 schrieb Chuck Swiger:
I have been trying to convince the "powers that be" that SCSI
would be much better.. but the price difference is just too
astronomical for the capacities we need (500GB to 2 TB)
Even 10K RPM IDE drives seem like would be a problem since they
are
13 matches
Mail list logo
