From: danielhilst@gmail.com (Daniel Hilst Selli)
To: kernelnewbies@lists.kernelnewbies.org
Subject: [rrd-users] Can small writes generate a lot of faults?
Date: Tue, 23 Apr 2013 12:53:13 -0300 [thread overview]
Message-ID: <5176AE69.10006@gmail.com> (raw)
In-Reply-To: <9358EF77-C6D9-495B-93DE-89994A121517@oetiker.ch>
Em 20/04/2013 09:09, Tobi Oetiker escreveu:
> hi daniel
>
> On 19.04.2013, at 16:42, Daniel Hilst Selli <danielhilst@gmail.com> wrote:
>
>> 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, ... !?
>>
> rrdtool changes just few bytes in the rrf file with each update
>
> the OS though can only write a complete block of data to disk.
>
> so when you write a byte to a file, the OS has to first fetch the block, modify the byte and write the block back
>
> that is why rrdtool benefits greatly from more RAM as it can hold mor blocks in RAM and does not have to read them first.
>
> cheers tobi
>
Thanks Tobi, I had no idea about this read/update/write process, Now I
know how to improve the performance of my
collectd+rrdtool stuff,
Cheers
prev parent reply other threads:[~2013-04-23 15:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-19 21:42 Can small writes generate a lot of faults? Daniel Hilst Selli
2013-04-21 21:53 ` 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 ` Daniel Hilst Selli [this message]
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=5176AE69.10006@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.