kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: danielhilst@gmail.com (Daniel Hilst Selli)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Can small writes generate a lot of faults?
Date: Fri, 19 Apr 2013 18:42:05 -0300	[thread overview]
Message-ID: <5171BA2D.1040305@gmail.com> (raw)

My case is this, I'm using collectd [1] with rrdtool [2] to monitor some 
server.
a) When I enable rrdtool plugin I can grab collectd process as top page 
fault process on top command.
PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  nFLT COMMAND
20128 root      18   0 4105m  35m  17m S  7.9  0.3 0:09.62  22k 
/opt/collectd/sbin/collectd
b) Disabling rrdtool plugin dramastically decrease the number of page 
faults of collectd.
c) I know that rrdtool plugin is known to generate a lot of small 
writes, as stated in [3]. Also I know the parameters to improving 
collectd's cache usage to save I/O, but this is not the question here..

AFAIK, major page faults are generated when data that is not yet present 
on RAM is loaded from disk, but in this case data is being write do 
disk, I can't
see how writes can generate faults, but still, it seems that is 
happening, ... !?

Is that possible?

Cheers,

[1] http://www.collectd.org
[2] http://oss.oetiker.ch/rrdtool/
[3] https://collectd.org/wiki/index.php/Inside_the_RRDtool_plugin

             reply	other threads:[~2013-04-19 21:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-19 21:42 Daniel Hilst Selli [this message]
2013-04-21 21:53 ` Can small writes generate a lot of faults? Gaurav Jain
2013-04-22  3:55 ` Mulyadi Santosa
2013-04-22 13:20   ` Greg Freemyer
2013-04-23 15:19     ` Daniel Hilst Selli
     [not found] ` <9358EF77-C6D9-495B-93DE-89994A121517@oetiker.ch>
2013-04-23 15:53   ` [rrd-users] " Daniel Hilst Selli

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=5171BA2D.1040305@gmail.com \
    --to=danielhilst@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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 NNTP newsgroup(s).