public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Cc: KH <gentoo-user@konstantinhansen.de>
Subject: Re: [gentoo-user] how to use RAM
Date: Tue, 13 Oct 2009 00:39:33 +0200	[thread overview]
Message-ID: <200910130039.33752.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <4AD3A913.3050500@konstantinhansen.de>

On Tuesday 13 October 2009 00:09:23 KH wrote:
> > I will give my virtual machines more RAM to improve their performance,
> > yes, this is maybe the main reason for me to upgrade RAM.
> > 
> > But are there any other things I might forget?
> > 
> > Are there any creative non-ricer ways to really make use of it?
> > 
> > I would like to hear your opinion on this, I am quite sure the
> > gentoo-community knows one trick or the other ;-)
> > 
> > Thanks a lot, Stefan
> > 
> 
> Hi,
> 
> you could regularly measure your disk speed by coping huge amounts of 
> data to a second ram-disk, and back. Then you have a good knowledge of 
> read and write speed of your hdd :-)
> 
> I often use the ram disk for creating iso images before burning them to 
> dvd/cd. This is a lot faster than doing this on an hdd.
> 

Just make sure the total amount of data is significantly larger than the 
amount of RAM, to negate the effect of in-RAM caching. A CD .iso for example 
can easily be cached in RAM as well as have the copy too. The write to hdd 
will be almost instant the second time

-- 
alan dot mckinnon at gmail dot com



  reply	other threads:[~2009-10-12 22:40 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-12 20:44 [gentoo-user] how to use RAM Stefan G. Weichinger
2009-10-12 21:52 ` [gentoo-user] " Nikos Chantziaras
2009-10-12 22:01   ` Stefan G. Weichinger
2009-10-12 22:09 ` [gentoo-user] " KH
2009-10-12 22:39   ` Alan McKinnon [this message]
2009-10-13 11:35     ` Stefan G. Weichinger
2009-10-12 22:45   ` Dale
2009-10-13  5:56     ` KH
2009-10-13 16:26 ` Joshua Murphy
2009-10-13 17:58   ` Stefan G. Weichinger
2009-10-14  0:03     ` Joshua Murphy
2009-10-14  7:18       ` Stefan G. Weichinger
2009-10-14  9:42         ` KH
2009-10-14 10:08           ` Stefan G. Weichinger
2009-10-14 10:25           ` Dale
2009-10-14 11:31             ` pk
2009-10-14 11:36               ` Alan McKinnon
2009-10-14 14:33               ` KH
2009-10-14 15:04                 ` Dale
2009-10-14 16:55                   ` Stefan G. Weichinger
2009-10-14 19:59                     ` Alan McKinnon
2009-10-14 20:31                       ` Stefan G. Weichinger
2009-10-14 20:21                     ` Volker Armin Hemmann
2009-10-14 20:28                       ` Stefan G. Weichinger
2009-10-14 20:38                         ` Volker Armin Hemmann
2009-10-14 20:43                           ` Stefan G. Weichinger
2009-10-14 20:34                       ` Alan McKinnon
2009-10-14 20:40                         ` Volker Armin Hemmann
2009-10-14 20:40                         ` Stefan G. Weichinger
2009-10-14 20:57                           ` Alan McKinnon
2009-10-14 20:48                         ` Neil Bothwick
2009-10-14 21:01                           ` Alan McKinnon
2009-10-15  1:24                         ` Stroller

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=200910130039.33752.alan.mckinnon@gmail.com \
    --to=alan.mckinnon@gmail.com \
    --cc=gentoo-user@konstantinhansen.de \
    --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