Date: Thu, 23 Jan 2020 14:40:17 +0100 (CET) From: Wojciech Puchar <wojtek@puchar.net> To: Miroslav Lachman <000.fbsd@quip.cz> Cc: Wojciech Puchar <wojtek@puchar.net>, freebsd-hackers@freebsd.org Subject: Re: slow directory operation on huge dirs Message-ID: <alpine.BSF.2.20.2001231437210.80825@puchar.net> In-Reply-To: <9b426949-be87-106a-46c3-f1b6a2e5bb83@quip.cz> References: <alpine.BSF.2.20.2001191930040.17538@puchar.net> <alpine.BSF.2.20.2001231245190.98419@puchar.net> <cf4d3d5f-6c9e-81cf-f6a2-ade177b9f8ff@quip.cz> <alpine.BSF.2.20.2001231411400.63433@puchar.net> <9b426949-be87-106a-46c3-f1b6a2e5bb83@quip.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
>> this part works fine. The problem begins where it's already cached. >> >> To get the problem you need BOTH of: >> >> - large maxvnodes like half million >> - large directory (in order of 100000 files) > > I remember very similar problem with slow access of directories with 80 000+ > files. It was always slow like frozen hell. There is some recommendation to first - we have DIRHASH option and i have it enabled. second - it is not just a problem of huge directory but both huge directory and large maxvnodes settings. Large directories works fast when kern.maxvnodes is small and there is enough dirhash_maxmem. it's clearly an error somewhere.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.20.2001231437210.80825>