smatch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Himanshu Jha <himanshujha199640@gmail.com>, smatch@vger.kernel.org
Subject: Hangs while building the cross function DB
Date: Mon, 28 Aug 2017 10:43:10 +0300	[thread overview]
Message-ID: <20170828074310.karya6frxeaz7x4j@mwanda> (raw)
In-Reply-To: <20170828064341.GA2506@himanshu-Vostro-3559>

Himanshu Jha had a question about hangs while building the cross
function DB.

Building the cross function DB used to hang my system for half an hour
but I kept tweaking it so now it's barely noticeable.  I have a quad
core with 32GB of RAM.  The problem is that Smatch is reading from the
warns.txt file and writing to smatch_db.sqlite file as fast as possible.
Both files are around 15-20GB.  This IO pattern is very hard on the
default Linux IO schedulers.

The BFQ scheduler is designed to fix these hangs, so your best bet is to
try that.
https://unix.stackexchange.com/questions/375600/how-to-enable-and-use-the-bfq-scheduler

regards,
dan carpenter


           reply	other threads:[~2017-08-28  7:43 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20170828064341.GA2506@himanshu-Vostro-3559>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170828074310.karya6frxeaz7x4j@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=himanshujha199640@gmail.com \
    --cc=smatch@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).