Date: Thu, 23 Jan 2020 14:12:54 +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.2001231411400.63433@puchar.net> In-Reply-To: <cf4d3d5f-6c9e-81cf-f6a2-ade177b9f8ff@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>
next in thread | previous in thread | raw e-mail | index | archive | help
>>> >> nobody have idea what's the problem? > > Is it "just slow" or is your disk too busy? (iostat) no. disk is idle, system CPU load takes half of system (8 cores)! > > Can it be that pre-cacheing on huge directory makes disk too busy because > there is too much to read? 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)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.20.2001231411400.63433>