From nobody Sun Aug 20 21:07:08 2023 X-Original-To: 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 4RTSq24jkQz4qjcb for ; Sun, 20 Aug 2023 21:07:10 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: from mail-oo1-xc2f.google.com (mail-oo1-xc2f.google.com [IPv6:2607:f8b0:4864:20::c2f]) (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 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4RTSq22jRfz3gh7 for ; Sun, 20 Aug 2023 21:07:10 +0000 (UTC) (envelope-from mjguzik@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-oo1-xc2f.google.com with SMTP id 006d021491bc7-570c856e946so522965eaf.2 for ; Sun, 20 Aug 2023 14:07:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1692565629; x=1693170429; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=FftWY4B7CNJaRTG+rbcDQdkdqI2+efcueYIVqGwe0Ss=; b=MANI4Bqvjbu6ap4GlK1NcRz+MOQONoTAZ/oar1qhn5CsBUWD8CEki8hC6J6OAS41Zo 0MKQKvlsaTepbClCTIdtJv3pXOqZdpjh4QeeBl/TQqrIw9keSmLY0n9gCf1m97IHso4v c0GhzMtS0pay9g9yX5AX6kk38b7zqvHFKpxjADMcqpB1fPIrDcf+6opMcrBcSRKLB54j pzD+5XK0+bzVkowPf4EQL+AOe8D3NJkpAuIrHHmcaCRcsaKWGmCkmsLrcRHP2TdVrtNi xFD285ectO6W03wQB2BWpzob3sM6FY+gi4LWtb0HuNIrPPcBtCb5hMycOFZXzVVHkFvj cygw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1692565629; x=1693170429; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=FftWY4B7CNJaRTG+rbcDQdkdqI2+efcueYIVqGwe0Ss=; b=BIwgY/yzjxV9ULyyjlMnlcNDDkLgiPf1Ue2RXW/Te3E6uEdGhlHEzMzZm4vORisLkX CR27Fh1covyx9QUjx+xzumBzQffMut6cxxEfsfbLW7ARYAkMy7qfZC4429OGMqDZ+E4v it4oQtuEF8kCONzqse174dNacNuWLp5fH/gUTFUPMVZMoTEiD313Y8GNwFOFLhWwhVjM UQVKMTOcEjTurMvbAHRF3XjgQ/x9IH8g5IXu9B8att86yrv9nfz0ISy2/oDuW8lIOnYq knAEe0iy1wtpFB2AMOiqT8Y4DTfGUiKIKAimCOeJ+RRPzELZwSgF29s3uRd9lSiSDq3L 0lZw== X-Gm-Message-State: AOJu0YwGOeAafadxlUphDeReQ0AMmKniY1dgfzhcGuegfjHvjPVxrl2/ 6HMxrPxOXgMQ+PXa3QY5ShkgfTWKw/eIFebuyac= X-Google-Smtp-Source: AGHT+IFkuu+mtxGlp9IaV30Ovl+7mRwPKtDgpyvTP+WjkqnRDeZAgO0+Comh5ei1tUzyMOTNOtbGsi+F11LIn+9QL1M= X-Received: by 2002:a4a:654e:0:b0:566:ed69:422d with SMTP id z14-20020a4a654e000000b00566ed69422dmr5556239oog.7.1692565629181; Sun, 20 Aug 2023 14:07:09 -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 Received: by 2002:ac9:79d9:0:b0:4f0:1250:dd51 with HTTP; Sun, 20 Aug 2023 14:07:08 -0700 (PDT) In-Reply-To: <58493b568dbe9fb52cc55de86e01f5e2@Leidinger.net> References: <61ca9df1b15c0e5477ff51196d0ec073@Leidinger.net> <88e837aeb5a65c1f001de2077fb7bcbd@Leidinger.net> <4d60bd12b482e020fd4b186a9ec1a250@Leidinger.net> <73f7c9d3db8f117deb077fb17b1e352a@Leidinger.net> <58493b568dbe9fb52cc55de86e01f5e2@Leidinger.net> From: Mateusz Guzik Date: Sun, 20 Aug 2023 23:07:08 +0200 Message-ID: Subject: Re: Speed improvements in ZFS To: Alexander Leidinger Cc: current@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4RTSq22jRfz3gh7 X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] On 8/20/23, Alexander Leidinger wrote: > Am 2023-08-20 22:02, schrieb Mateusz Guzik: >> On 8/20/23, Alexander Leidinger wrote: >>> Am 2023-08-20 19:10, schrieb Mateusz Guzik: >>>> On 8/18/23, Alexander Leidinger wrote: >>> >>>>> I have a 51MB text file, compressed to about 1MB. Are you interested >>>>> to >>>>> get it? >>>>> >>>> >>>> Your problem is not the vnode limit, but nullfs. >>>> >>>> https://people.freebsd.org/~mjg/netchild-periodic-find.svg >>> >>> 122 nullfs mounts on this system. And every jail I setup has several >>> null mounts. One basesystem mounted into every jail, and then shared >>> ports (packages/distfiles/ccache) across all of them. >>> >>>> First, some of the contention is notorious VI_LOCK in order to do >>>> anything. >>>> >>>> But more importantly the mind-boggling off-cpu time comes from >>>> exclusive locking which should not be there to begin with -- as in >>>> that xlock in stat should be a slock. >>>> >>>> Maybe I'm going to look into it later. >>> >>> That would be fantastic. >>> >> >> I did a quick test, things are shared locked as expected. >> >> However, I found the following: >> if ((xmp->nullm_flags & NULLM_CACHE) != 0) { >> mp->mnt_kern_flag |= >> lowerrootvp->v_mount->mnt_kern_flag & >> (MNTK_SHARED_WRITES | MNTK_LOOKUP_SHARED | >> MNTK_EXTENDED_SHARED); >> } >> >> are you using the "nocache" option? it has a side effect of xlocking > > I use noatime, noexec, nosuid, nfsv4acls. I do NOT use nocache. > If you don't have "nocache" on null mounts, then I don't see how this could happen. -- Mateusz Guzik