From owner-freebsd-questions@FreeBSD.ORG Sun Mar 17 03:15:16 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id C156F5C9 for ; Sun, 17 Mar 2013 03:15:16 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: from mail-ve0-f174.google.com (mail-ve0-f174.google.com [209.85.128.174]) by mx1.freebsd.org (Postfix) with ESMTP id 6F83AEA0 for ; Sun, 17 Mar 2013 03:15:15 +0000 (UTC) Received: by mail-ve0-f174.google.com with SMTP id pb11so3605662veb.33 for ; Sat, 16 Mar 2013 20:15:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=SXJ1GsChoLxKpDT6U6hapL7XWTvYVwA6lMIG6MkCHUQ=; b=X1BGju9wPVH8IspD7G3Wd5k5DSKglf5+wjAn/IpNAe4Wg6SWexF8lj0FmeMkS0Sqp2 lfcC5Wc00pP1veAotI45zAhtdYgHNT/ZcVtgGmyro1EB5AaQ1tRhvN3fmjok8ZnDLs7W nulQYoedjwj57YxSjmUPphSo9uZYmoV+vaE3kpCWcnk3Qk+cbGR18Ptr66wi4NkB2Mxj dHD+rm0w4d3/XnUYriQ8bytjs7GHPVtKbYF9GzqXuaEqbDG+9ftEWYoB31n9cqgevuvm qqSf1UYrt8sPhx6B4Y4W848ryoRxioQGQGBZH8J5HsdAucB/Q+106RplThkBoTuP5sSn Y13w== MIME-Version: 1.0 X-Received: by 10.220.40.9 with SMTP id i9mr13771921vce.23.1363490109720; Sat, 16 Mar 2013 20:15:09 -0700 (PDT) Received: by 10.58.132.203 with HTTP; Sat, 16 Mar 2013 20:15:09 -0700 (PDT) In-Reply-To: <51452080.7090909@tundraware.com> References: <5144BEB7.3090906@tundraware.com> <5144ED13.7020808@tundraware.com> <51452080.7090909@tundraware.com> Date: Sat, 16 Mar 2013 20:15:09 -0700 Message-ID: Subject: Re: NFS Performance: Weirder And Weirder From: Mehmet Erol Sanliturk To: Tim Daneliuk Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD Mailing List X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Mar 2013 03:15:16 -0000 On Sat, Mar 16, 2013 at 6:46 PM, Tim Daneliuk wrote: > On 03/16/2013 05:43 PM, Mehmet Erol Sanliturk wrote: > >> >> > Michael W. Lucas in Absolute FeeBSD , 2nd Edition , ( ISBN : >> 978-1-59327-151-0 ) , >> is suggesting the following ( p. 248 ) : >> >> In client ( mount , or , fstab ) , use options ( -o tcp , intr , soft , >> -w=32768 , -r=32768 ) >> >> tcp option will request a TCP mount instead of UDP mount , because >> FreeBSD NFS defaults to running over UDF . >> >> This subject may be another check point . >> >> > > Another very good suggestion but ... to no avail. Thanks for pointing > this out. > > -- > ------------------------------**------------------------------** > ---------------- > Tim Daneliuk tundra@tundraware.com > PGP Key: http://www.tundraware.com/PGP/ > > I have read messages once more . There is a phrase : Linux Mint 12 machineS ( plural ) . In your descriptions , there is no any information about network setup : Single client , multiple clients , etc . Then , with some assumptions : If there is ONLY ONE client , and all of the tests are performed on this ONLY client , problem may be attributed to FreeBSD server or kind of file(s) in different directories : One of the is encrypted ( requires decryption ) , another is plain file , etc. . If there is MORE than ONE client , problem may be attributed to any one the components of the network ( server , clients , switch , cable , NICs , interfering other software , etc. ) . Assume there is MULTIPLE clients : Take two clients of them : (A) Client 1 : Mount two directories . (B) Client 2 : Mount two directories . Test transmission performance : If they are similar , inspect server settings , directory privileges , etc . , file systems ( one is ZFS , other is UFS2 , etc. ) . All of the hardware may work properly , but if the file reading is not able to feed NIC sufficiently fast , it may show up as degraded performance . Increasing NIC buffer size ( as standard it is around 1000 bytes ) to maximum available , may offset latency of supply of data to NIC . If they are different : Check client specialties : A cable may be CAT5 ( only maximum 100 Mbits transfer . Network cards are adaptive , they try 1 Gbits , if it is not achievable , it reduces to speed to 100 Mbits , even to 10 Mbits ) . In that case either use CAT6 cable or CAT5x ( for 1 Gbit transmission , I do not remember x now ) The cable kind should be written on cable , if it is not written , select a properly labelled cable . Interchange cable tips to clients : If performance interchanges also : Cable or SWITCH port is faulty : Check switch port : It may be a 100 Mbits , be sure that it is also 1 Gbits and working properly . Mehmet Erol Sanliturk