From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: aligning SSD partitions
Date: Thu, 06 Sep 2012 09:27:23 -0500 [thread overview]
Message-ID: <5048B2CB.5000902@gmail.com> (raw)
In-Reply-To: <20120906132735.GG2442@nicolas-desktop>
Nicolas Sebrecht wrote:
> The 06/09/12, Dale wrote:
>
>> I do get it. I CLEARED #1 and #2, there is no usage of #3 and #4 is not
>> large enough here to matter. So, it is left with #5.
>>
>> See the point? The test was a NORMAL emerge with portages work
>> directory on tmpfs and a NORMAL emerge with portages work directory on
>> disk and compare the results. The test resulted in little if any
>> difference.
>>
>> If I ran the test and did not clear the cache, then I would expect
>> skewed results because after the first emerge, some files would be
>> cached in ram and the drive would not be used. If you clear the cache,
>> then it has to take the same steps regardless of whether it was run
>> first, second or third time.
> What you want to measure is the difference of times required by emerge
> whether you use a real disk or tmpfs as backend.
>
> What you would expect is a difference because a disk is much slower than
> RAM.
>
> What you see is no difference. You won't conclude that disk is as fast
> as RAM, right? Can you explain why you don't see much difference? No.
>
> Here is the explanation: if you have enough RAM, the emerge rapidity
> will NOT rely on the disk rapidity whatever storage backend you use. It
> will only rely on the RAM rapidity because of the kernel cache.
>
> Now, pretending that whatever backend you use (real disk or tmpfs) never
> changes the emerge time is WRONG because of the persistence strategy
> used by the kernel for the kernel cache.
>
> When having lot of RAM like you have, the persistence strategy of the
> kernel cache is NEVER raised in the process.
>
> This is exactly what your tests demonstrate demonstrate: if you have
> enough RAM, the persistence strategy of kernel cache is not raised, so
> everything happens in RAM, so the emerge times do not differ.
>
The end result is this, it doesn't matter if portage's work directory is
on tmpfs or not. You just concluded that yourself which is what I have
been saying. It doesn't matter WHY it doesn't matter, it just matters
that it DOESN'T matter. It takes just as long on a system with
portage's work directory on tmpfs as it does on tmpfs. Very little
difference at all. The variance I had was minimal at best. It was
basically seconds of difference not minutes.
I might add, I got the same results on my older system which has a LOT
less ram. I think it only has 2Gbs or so.
Dale
:-) :-)
--
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
next prev parent reply other threads:[~2012-09-06 14:34 UTC|newest]
Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-04 7:20 [gentoo-user] aligning SSD partitions Philip Webb
2012-09-04 7:47 ` Neil Bothwick
2012-09-04 20:31 ` Volker Armin Hemmann
2012-09-04 20:58 ` Neil Bothwick
2012-09-04 21:00 ` Neil Bothwick
2012-09-04 21:52 ` Peter Humphrey
2012-09-05 0:42 ` Philip Webb
2012-09-05 8:23 ` Neil Bothwick
2012-09-05 9:02 ` Philip Webb
2012-09-05 9:23 ` Peter Humphrey
2012-09-05 11:07 ` Dale
2012-09-05 11:25 ` Peter Humphrey
2012-09-05 12:02 ` Dale
2012-09-05 12:58 ` Peter Humphrey
2012-09-05 18:02 ` Dale
2012-09-05 19:01 ` Paul Hartman
2012-09-05 20:46 ` Dale
2012-09-05 21:22 ` Paul Hartman
2012-09-05 22:36 ` Peter Humphrey
2012-09-05 12:31 ` Neil Bothwick
2012-09-05 12:52 ` Dale
2012-09-05 15:17 ` Neil Bothwick
2012-09-05 15:23 ` Michael Mol
2012-09-05 17:54 ` Dale
2012-09-05 23:42 ` Neil Bothwick
2012-09-06 9:13 ` Dale
2012-09-06 6:57 ` [gentoo-user] " Nicolas Sebrecht
2012-09-06 9:15 ` Dale
2012-09-06 9:47 ` Neil Bothwick
2012-09-06 10:03 ` Dale
2012-09-06 10:18 ` Neil Bothwick
2012-09-06 10:56 ` Dale
2012-09-06 10:41 ` Nicolas Sebrecht
2012-09-06 11:03 ` Dale
2012-09-06 11:37 ` Nicolas Sebrecht
2012-09-06 12:21 ` Dale
2012-09-06 13:27 ` Nicolas Sebrecht
2012-09-06 14:27 ` Dale [this message]
2012-09-06 10:11 ` Dale
2012-09-06 10:20 ` Neil Bothwick
2012-09-06 10:44 ` Dale
2012-09-06 11:11 ` Nicolas Sebrecht
2012-09-06 11:31 ` Dale
2012-09-06 12:17 ` Neil Bothwick
2012-09-06 12:44 ` Nicolas Sebrecht
2012-09-06 12:48 ` Dale
2012-09-06 13:04 ` Neil Bothwick
2012-09-06 14:07 ` Dale
2012-09-06 14:26 ` Michael Mol
2012-09-06 16:27 ` Dale
2012-09-07 7:56 ` Nicolas Sebrecht
2012-09-07 9:15 ` Nicolas Sebrecht
2012-09-07 12:25 ` Dale
2012-09-07 19:48 ` Neil Bothwick
2012-09-06 14:37 ` Neil Bothwick
2012-09-06 16:32 ` Dale
2012-09-06 20:21 ` Neil Bothwick
2012-09-06 14:51 ` Nicolas Sebrecht
2012-09-06 16:49 ` Dale
2012-09-06 13:46 ` Nicolas Sebrecht
2012-09-06 14:20 ` Dale
2012-09-06 14:33 ` Michael Mol
2012-09-06 16:39 ` Dale
2012-09-06 16:00 ` Paul Hartman
2012-09-06 16:44 ` Dale
2012-09-06 20:21 ` Neil Bothwick
2012-09-06 21:09 ` Dale
2012-09-06 22:38 ` Neil Bothwick
2012-09-06 23:08 ` Dale
2012-09-07 7:47 ` Nicolas Sebrecht
2012-09-07 12:35 ` Dale
2012-09-10 10:32 ` Nicolas Sebrecht
2012-09-10 11:13 ` Dale
2012-09-10 12:37 ` Michael Mol
2012-09-10 13:52 ` Dale
2012-09-10 14:02 ` Michael Mol
2012-09-10 14:22 ` Dale
2012-09-05 12:55 ` [gentoo-user] " Adam Carter
2012-09-05 15:28 ` Florian Philipp
2012-09-05 9:26 ` Neil Bothwick
2012-09-05 16:30 ` Volker Armin Hemmann
2012-09-05 17:02 ` Neil Bothwick
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=5048B2CB.5000902@gmail.com \
--to=rdalek1967@gmail.com \
--cc=gentoo-user@lists.gentoo.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