From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from wout2-smtp.messagingengine.com ([64.147.123.25]:44597 "EHLO wout2-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726342AbeLAVNI (ORCPT ); Sat, 1 Dec 2018 16:13:08 -0500 From: Nikolaus Rath To: Miklos Szeredi Cc: fuse-devel , linux-fsdevel@vger.kernel.org Subject: Re: [fuse-devel] [fuse] Unexpectedly large number of getattr() and lookup requests References: <87va4fbmxp.fsf@vostro.rath.org> Date: Sat, 01 Dec 2018 10:00:55 +0000 In-Reply-To: (Miklos Szeredi's message of "Fri, 30 Nov 2018 08:58:33 +0100") Message-ID: <87muppbm7c.fsf@vostro.rath.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Nov 30 2018, Miklos Szeredi wrote: > On Thu, Nov 29, 2018 at 10:20 PM Nikolaus Rath wrote: >> >> Hello, >> >> I am seeing an unexpectedly large number of getattr() and lookup() >> requests being sent to userspace fuse. I am setting a very large >> attr_timeout and entry_timeout, so I would have expected that the >> maximum number of getattr() and lookup() requests is capped by the >> number of distinct files in the filesystem plus the number of forget >> requests. >> >> However, actual numbers are much higher. For example, when running tests >> on a filesystem with 2960 directory entries, I am getting scenarios >> with 203447 lookup requests, 12970 getattr requests, and zero forget >> requests. >> >> Did I misunderstand something about how dentry and attribute caching >> works? > > Debug log might be useful. Here you go! https://www.dropbox.com/s/tg4vyshz4g18sub/fuse-debug.log.xz?dl=3D1 Best, -Nikolaus --=20 GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F =C2=BBTime flies like an arrow, fruit flies like a Banana.=C2= =AB