From owner-freebsd-current@FreeBSD.ORG Wed Jul 27 02:28:04 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6CEB4106566C; Wed, 27 Jul 2011 02:28:04 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id 184CE8FC15; Wed, 27 Jul 2011 02:28:03 +0000 (UTC) Received: by gyf3 with SMTP id 3so956179gyf.13 for ; Tue, 26 Jul 2011 19:28:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=tLhPL3U9r5xEFzf/C1seLSpczzjdFqU5ZCdo/NUHFC0=; b=xcjk/Jf3C4XYI9Gp71qBOMuzP+i/hULufw/BPKo/MdJ5ydv9FgV3qBWFhfcXNx3nQb MlOh9b4GEAB7rat7DNhuFgTb+QErUT0zcjkOycXu481nMRDgUIKw9YPizayuZAsMk/0y u2t9YCl//CE0oLy4+TvEvxip0yIvMfuHRKfBE= MIME-Version: 1.0 Received: by 10.150.72.23 with SMTP id u23mr3345939yba.443.1311733683320; Tue, 26 Jul 2011 19:28:03 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.150.197.5 with HTTP; Tue, 26 Jul 2011 19:28:03 -0700 (PDT) In-Reply-To: <20110727004850.GA63109@freebsd.org> References: <20110724212544.GA57733@freebsd.org> <20110725072102.GA24938@freebsd.org> <4E2D2C32.5010602@gmx.de> <20110727004850.GA63109@freebsd.org> Date: Wed, 27 Jul 2011 10:28:03 +0800 X-Google-Sender-Auth: DKoVhWZk8jIwxJVms-cOLaLPNJg Message-ID: From: Adrian Chadd To: Alexander Best Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Norberto Lopes , Matthias Andree , freebsd-current@freebsd.org Subject: Re: chromium port causing massive I/O faults X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jul 2011 02:28:04 -0000 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 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 >