Date: Wed, 27 Jul 2011 10:28:03 +0800 From: Adrian Chadd <adrian@freebsd.org> To: Alexander Best <arundel@freebsd.org> Cc: Norberto Lopes <nlopes.ml@gmail.com>, Matthias Andree <matthias.andree@gmx.de>, freebsd-current@freebsd.org Subject: Re: chromium port causing massive I/O faults Message-ID: <CAJ-Vmom9ZoVt=4Dk4SGpP%2Bj3Sb4WfMybeP7ebbdC4hQ0UKibRQ@mail.gmail.com> In-Reply-To: <20110727004850.GA63109@freebsd.org> References: <20110724212544.GA57733@freebsd.org> <CAJ-VmonHcDM_p3%2BYPO2vyF9a054VavQmVQqcKt369w28M%2BtaXg@mail.gmail.com> <20110725072102.GA24938@freebsd.org> <4E2D2C32.5010602@gmx.de> <20110727004850.GA63109@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Again, if it's doing lots of mmap based IO, it's likely not a big deal. Try getting dtrace to give you useful info? Adrian On 27 July 2011 08:48, Alexander Best <arundel@freebsd.org> wrote: > On Mon Jul 25 11, Matthias Andree wrote: >> Am 25.07.2011 09:21, schrieb Alexander Best: >> > On Mon Jul 25 11, Adrian Chadd wrote: >> >> Is it perhaps doing disk IO using mmap? >> > >> > how can i check, whether that's the case or not? >> >> Use truss(1) for instance. >> >> However, unless there are *practical* problems, a high number of page >> faults is not an indication for problems. =A0Although it may sound scary= , >> page faults are a feature of the memory management. > > unfortunately truss(1) is crashing chromium :( i opened up a new thread > reagarding this issue on freebsd-current@. > > another thing i noticed is the increase in system calls caused by chromiu= m. > let's have a look at hub.freebsd.org: > > uptime =3D 149 days > > and 'vmstat -s' reports: > > 2168697753 cpu context switches > 2266220366 device interrupts > 2902880931 software interrupts > 3779075897 traps > 902107847 system calls > > now on my box: > > uptime =3D 2 days > > and 'vmstat -s' reports: > > 1155995386 cpu context switches > 164577882 device interrupts > 189456976 software interrupts > 137007580 traps > 2178434582 system calls > > i ran the following command twice. first time without running chromium an= d the > second time with chromium running: > > otaku% vmstat -s|grep "system calls"; sleep 1; vmstat -s|grep "system cal= ls" > 2178187850 system calls > 2178189739 system calls > > otaku% vmstat -s|grep "system calls"; sleep 1; vmstat -s|grep "system cal= ls" > 2177998835 system calls > 2178022003 system calls > > so it's 2k/sec vs. 23k/sec!!!! > > cheers. > alex >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmom9ZoVt=4Dk4SGpP%2Bj3Sb4WfMybeP7ebbdC4hQ0UKibRQ>