From nobody Thu Oct 7 07:42:32 2021 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4557012D6F40 for ; Thu, 7 Oct 2021 07:43:10 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: from mail-ua1-x931.google.com (mail-ua1-x931.google.com [IPv6:2607:f8b0:4864:20::931]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HQ3G53yPNz3stD for ; Thu, 7 Oct 2021 07:43:09 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: by mail-ua1-x931.google.com with SMTP id i8so3640394uae.7 for ; Thu, 07 Oct 2021 00:43:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=c9KjjB95U6XLqhGIRt3PkrrzASD007oQN2sfj3BnpCI=; b=B3XOnlhVIDoCh4Z/cYJQo95qtb1cUbRvVBCjjWhofvgFbOTfAG+XztrfUysLvkZQGS gTHSnp+NhUT7Q0wdjjwEV9DzSAPZfW0adPfX+bc1X/VwKT2TtDsvFEZYqj9zAJwaCA5n L0O3OMBpddBijQFv9D3Q4h587oKzheIetMGVLP9gN6j6qEUZ9gptjdnuJdVvjXjKRLI6 4uDyAoyXUqrioCfrWjfLJFxP6emb06EDLAQHxKhusM66MzIn9k7lq/fHqQ1XdDkfFDov NVK5E74ddJS8IX2mOCh9Ij8iusiAogRPYVeI6wfA1CiJcSF5wSezsTmywt+OUSSIggYD Nc6g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=c9KjjB95U6XLqhGIRt3PkrrzASD007oQN2sfj3BnpCI=; b=6unNYEpnFZWvbcIOkGoSMDv0qFIJ1Mr1j2Ed+nRLiohT8gW0rUURo5v/S41jFx0xU7 IO3ov9TBfNgzw9v6+4vL5NDuv1q6UrVvMHsU1Iqe1fBNm7Dhv/r2WXU7Izg/o/Y1jYri yXiKUVUqlQrxjcBwaB+c2uLz+lX8ISCeDyRaQ0LNb/e86KGsmHjnKAXYhREuJ40mOtsz VieRut5sZ0m1BVaKRBEj9BvDAV88hiLOSM+SEhedk26Q6Q7f2+98lPb3k5gPsZUeW2LI ZdGaddp8vFmoszwgbHxYxNV9WX7qP05Mcx0Gj7Co1cqzwJ0ped55t8ppW+bB/AeBCqL5 204w== X-Gm-Message-State: AOAM531k4nllP7n/yeSnSA7HfgXQHB63QK7/FAkDje6lH63Ia9ArvGes NSnZu2l7yRlX2D2q3V4W7BOWCFFJRDj/AQS2HtfXG4JKZ58= X-Google-Smtp-Source: ABdhPJzNL12t5xaGacZj13ol/sbIA9jJrJyXE/IHJ4mu6TzY13aQFhx2EfjCAJU+JGpjFTrYQATXgzoAFiuJZbzJcrk= X-Received: by 2002:ab0:6dd0:: with SMTP id r16mr2923901uaf.82.1633592588715; Thu, 07 Oct 2021 00:43:08 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: <20211007021643.bwglyvrswk2nm3fl@nexus.home.palmen-it.de> In-Reply-To: <20211007021643.bwglyvrswk2nm3fl@nexus.home.palmen-it.de> From: Mehmet Erol Sanliturk Date: Thu, 7 Oct 2021 10:42:32 +0300 Message-ID: Subject: Re: Writing large build logs to NFS extremely slow? To: FreeBSD Current Content-Type: multipart/alternative; boundary="000000000000f54a9405cdbe6906" X-Rspamd-Queue-Id: 4HQ3G53yPNz3stD X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b=B3XOnlhV; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of mesanliturk@gmail.com designates 2607:f8b0:4864:20::931 as permitted sender) smtp.mailfrom=mesanliturk@gmail.com X-Spamd-Result: default: False [-1.59 / 15.00]; FREEMAIL_FROM(0.00)[gmail.com]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; URI_COUNT_ODD(1.00)[1]; MID_RHS_MATCH_FROMTLD(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-0.59)[-0.590]; FROM_EQ_ENVFROM(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; TAGGED_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20210112]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::931:from]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-Spam: Yes X-ThisMailContainsUnwantedMimeParts: Y --000000000000f54a9405cdbe6906 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Oct 7, 2021 at 5:17 AM Felix Palmen wrote: > Hi all, > > I use a -CURRENT bhyve vm for testing port builds with poudriere. As > this vm is only running when needed, but I want to always have access to > the build logs, I use NFS to mount /usr/local/poudriere/data/logs from > the host. > > I noticed some few ports take ridiculously long to build while barely > using any CPU time at all. On a closer look, that's all ports producing > a lot of compiler (warning) output, e.g. gcc, gnutls, gtk2, =E2=80=A6 > > So I assume appending to a large file via NFS gets slower and slower. Is > there any mount option I could try to fix this? Right now I only have > `nolockd`, I also tried `noncontigwr` which didn't change anything. > > Thinking about alternatives to NFS, are there any news for client-side > 9p virtfs? I found which > still builds with a few minor adaptions, but trying to mount a 9p share > freezes the machine. > > Would you suggest a different mailing list to ask? > > BR, Felix > > -- > Dipl.-Inform. Felix Palmen ,.//.......... > {web} http://palmen-it.de {jabber} [see email] ,//palmen-it.de > {pgp public key} http://palmen-it.de/pub.txt // """"""""""" > {pgp fingerprint} A891 3D55 5F2E 3A74 3965 B997 3EF2 8B0A BC02 DA2A > I have encountered such cases previously , but I am not able to remember which parameters I have used to solve this problem , because I am not using the FreeBSD server now . A similar problem occurs also in the Linux NFS server. The problem is caused mainly by NFS definition parameters . If you study NFS definition parameters one by one , I think you will be able to find which one is effective . My opinion is the one setting is "write directly to disk" , i.e. , "do not use the cache" . In the "write directly to disk" case , without completion of a write , the computer in use is waiting for completion of previous write operation before writing a new record . This is useful in case of abrupt program terminations because every record is written into the disk file , by consuming more time . In the cache use case , time is not consumed much but the last written records are lost in an abrupt program termination . My understanding from your question is this . Mehmet Erol Sanliturk --000000000000f54a9405cdbe6906--