From: App Des <app4des@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] gentoo on ssds? intel anyone?
Date: Sun, 22 Nov 2009 12:54:48 +0200 [thread overview]
Message-ID: <417164300911220254ifdcbe1eh56786b6ea13c749b@mail.gmail.com> (raw)
In-Reply-To: <4B05CB09.20209@xunil.at>
[-- Attachment #1: Type: text/plain, Size: 1726 bytes --]
I think that buying an SSD right now is not worth it. If you are going to
buy one, get the intel G2 ones, but in my opinion it is always better to
first max out your RAM in your PC. After all the SSD is going to help when
you first boot your PC or open a program. After that everything is cached in
RAM and there will be no speed difference. Only in the rare case that you
use so many programs (that don't fit in cache) and compile things everyday
(which messes up the cache) you are going to need it.
Also you don't need to mess with many fstab/scheduler settings, it is not
worth it imo. Just add "noatime" to your favorite file system and you are
good to go.
On Fri, Nov 20, 2009 at 12:47 AM, Stefan G. Weichinger <lists@xunil.at>wrote:
>
> Greets, gentoo-users,
> I hope not to bring up some boring ricer-topic ;-)
>
> I am thinking of getting one of those shiny new SSDs for my main
> workstation. Not that I really *need* it, my box is performing well, I
> admit that I am curious and somehow childish ... some way of getting
> myself a christmas present or something like that ...
>
> anyway
>
> Although I read of Intel's various firmware-problems with their SSDs, I
> tend to buy one of their 80GB X25-M G2 Postville SSDs.
>
> I definitely *know* that I will shake my head a few months later at how
> I could spend that much money for those few and slow gigs of ssd ... but
> ... (think 100$ for 128MB usb-stick ... you know ...)
>
> I think of using that ssd for my gentoo-os-partition(s) and I wonder if
> one of you is already doing that. And I would like to hear of any
> problems/blockers/sensations this brings.
>
> Thanks for any infos, I'd be happy to hear whatever your experience is ...
>
> Stefan
>
>
>
[-- Attachment #2: Type: text/html, Size: 2133 bytes --]
next prev parent reply other threads:[~2009-11-22 12:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-19 22:47 [gentoo-user] gentoo on ssds? intel anyone? Stefan G. Weichinger
2009-11-19 23:05 ` Volker Armin Hemmann
2009-11-20 10:46 ` Stefan G. Weichinger
2009-11-20 14:38 ` [gentoo-user] " James
2009-11-20 17:43 ` Paul Hartman
2009-12-16 18:32 ` [gentoo-user] " Stefan G. Weichinger
2009-11-20 4:48 ` [gentoo-user] " Holger Hoffstaette
2009-11-20 9:09 ` Remy Blank
2009-11-20 10:45 ` Stefan G. Weichinger
2009-12-04 15:29 ` Stefan G. Weichinger
2009-12-04 20:30 ` [gentoo-user] " Holger Hoffstaette
2009-12-06 10:37 ` Stefan G. Weichinger
2009-11-22 10:54 ` App Des [this message]
2009-12-18 22:31 ` [gentoo-user] " Stefan G. Weichinger
2009-12-19 8:08 ` Stroller
2009-12-19 10:19 ` Stefan G. Weichinger
2009-12-20 7:14 ` Alan McKinnon
2009-12-25 10:37 ` Stefan G. Weichinger
2010-01-04 20:50 ` Stefan G. Weichinger
2010-01-19 11:53 ` Stefan G. Weichinger
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=417164300911220254ifdcbe1eh56786b6ea13c749b@mail.gmail.com \
--to=app4des@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