Date: Sat, 02 Jul 2016 17:24:12 -0700 From: Matthew Macy <mmacy@nextbsd.org> To: "chromium" <chromium@freebsd.org> Subject: chrome spends all its time calling close Re: chrome spends all its time calling open Message-ID: <155ae2426da.ecd708a055370.6844710089510046027@nextbsd.org> In-Reply-To: <155ae2351dc.d435e15355364.689950361019774764@nextbsd.org> References: <155ae2351dc.d435e15355364.689950361019774764@nextbsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Subject line was wrong.
---- On Sat, 02 Jul 2016 17:23:18 -0700 Matthew Macy <mmacy@nextbsd.org> wrote ----
>
> While looking at other issues I tried running truss on chrome at startup and I discovered a certain rather dysfunctional behavior:
>
>
> lanecrash# grep "close(" chrome.log | wc
> 1317903 7905445 68502169
> planecrash# wc chrome.log
> 1466068 8798135 78854285 chrome.log
>
> It repeatedly calls close on 1 up to ~128000. System calls aren't expensive per se, but if almost 95% of your system calls are close you're doing something quite wrong.
>
> -M
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?155ae2426da.ecd708a055370.6844710089510046027>