On 09/26/2011 04:46 PM, Terry Barnaby wrote:
> Thanks for the info. Might try that, but I still need NFS for other systems
> and having used it for almost 30 years am a bit used to it !
glusterfs and nfs mix nicely - you can use the native glusterfs client
(I do), or you can use an nfs client to
On 09/26/2011 01:08 PM, Dr. Michael J. Chudobiak wrote:
> On 09/25/2011 05:45 AM, Terry Barnaby wrote:
>> Anyone know why the NFS write performance with Fedora14 may be slow (without
>> async) ?
>> I have Gigabit networking which is all working fine and the systems in
>> question
>> have been runn
On 09/25/2011 05:45 AM, Terry Barnaby wrote:
> Anyone know why the NFS write performance with Fedora14 may be slow (without
> async) ?
> I have Gigabit networking which is all working fine and the systems in
> question
> have been running Fedora in various forms for many years.
I found NFSv4 to b
Terry Barnaby beam.ltd.uk> writes:
> ...
> Anyway a test with local nfs:
> time tar -xf /tmp/jpgraph-3.5.0b1.tar
> real3m27.320s
> ...
Do it for both, NFS v3 and v4. It may provide an additional regression case.
Filing BZ report will get you some answer from an NFS dev.
JB
--
users ma
On 09/25/2011 07:03 PM, Don Quixote de la Mancha wrote:
> Try writing to a different type of filesystem. It might be the
> filesystem's fault. MacTCP on the Classic Mac OS got a real bad rap
> because FTP writes were very slow, but it was easy to show that the
> problem was in the Heirarchical Fi
On 09/25/2011 06:41 PM, JB wrote:
> Terry Barnaby beam.ltd.uk> writes:
>
>> ...
>> # Test1, defaults: nfs version 4, sync
>> Server /etc/exports: "/data *.kingnet(rw)"
>> Client /etc/fstab: "king.kingnet:/data /data nfs defaults 0 0"
>>
>> dd if=/tmp/data.bin of=/data/tmp/data.bin bs=102400
>>
On 09/25/2011 06:13 PM, Don Quixote de la Mancha wrote:
> Are you using userspace NFS or the kernel NFS? The kernel NFS
> _should_ be faster.
>
> On Sun, Sep 25, 2011 at 10:02 AM, Terry Barnaby wrote:
>> I wonder if NFS is doing a complete sync() to disk on each file close ??
>
> If you are using
Try writing to a different type of filesystem. It might be the
filesystem's fault. MacTCP on the Classic Mac OS got a real bad rap
because FTP writes were very slow, but it was easy to show that the
problem was in the Heirarchical Filesystem.
Is your destination filesystem journaled? Maybe flus
Terry Barnaby beam.ltd.uk> writes:
> ...
> # Test1, defaults: nfs version 4, sync
> Server /etc/exports: "/data *.kingnet(rw)"
> Client /etc/fstab:"king.kingnet:/data /data nfs defaults 0 0"
>
> dd if=/tmp/data.bin of=/data/tmp/data.bin bs=102400
> 32.9 MB/s
>
> dd if=/data/tmp/data.bin o
Are you using userspace NFS or the kernel NFS? The kernel NFS
_should_ be faster.
On Sun, Sep 25, 2011 at 10:02 AM, Terry Barnaby wrote:
> I wonder if NFS is doing a complete sync() to disk on each file close ??
If you are using the userspace NFS, the strace command will show all
the system cal
On 09/25/2011 04:39 PM, JB wrote:
> Terry Barnaby beam.ltd.uk> writes:
>
>> ...
>
> It would be useful to publish a test for
> # Test4, defaults: nfs version 3
> that is with "sync" option, so we could see if similar degradation was
> present with older protocol ?
>
> One other thing: it would b
Terry Barnaby beam.ltd.uk> writes:
> ...
It would be useful to publish a test for
# Test4, defaults: nfs version 3
that is with "sync" option, so we could see if similar degradation was
present with older protocol ?
One other thing: it would be interesting to see the results if instead of
in-p
Anyone know why the NFS write performance with Fedora14 may be slow (without
async) ?
I have Gigabit networking which is all working fine and the systems in question
have been running Fedora in various forms for many years.
Writing a single large file across NFS is fine, about: 32MBytes/sec witho
13 matches
Mail list logo
