From: Stan Hoeppner <stan@hardwarefreak.com>
To: Jay Ashworth <jra@baylink.com>, xfs <xfs@oss.sgi.com>
Subject: Re: [xfs_check Out of memory: ]
Date: Sat, 28 Dec 2013 16:01:43 -0600 [thread overview]
Message-ID: <52BF4A47.3010604@hardwarefreak.com> (raw)
In-Reply-To: <23931797.1848.1388252140769.JavaMail.root@benjamin.baylink.com>
On 12/28/2013 11:35 AM, Jay Ashworth wrote:
> ----- Original Message -----
>> From: "Stan Hoeppner" <stan@hardwarefreak.com>
>
>> Create a 100GB swap partition and leave the remainder unallocated. The
>> unallocated space will automatically be used for GC and wear leveling,
>> increasing the life of all cells in the drive.
>
> *Great* tip. :-)
It's not so much of a tip but simply re-stating common knowledge, or
what should be by now. Over provisioning of SSDs has been written about
pretty extensively.
One benefit of over provisioning I failed to mention above is that it
also typically decreases the latency and increases the throughput of
random writes significantly. Linux swap writes tend to be sequential,
so this aspect of over provisioning won't pay dividends for the OP's use
case.
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-12-28 22:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-27 6:48 [xfs_check Out of memory: ] Stor??
2013-12-27 7:41 ` Jeff Liu
2013-12-27 8:07 ` Arkadiusz Miśkiewicz
2013-12-27 22:42 ` Dave Chinner
2013-12-27 23:20 ` Arkadiusz Miśkiewicz
2013-12-28 16:55 ` Stan Hoeppner
2013-12-28 17:35 ` Jay Ashworth
2013-12-28 22:01 ` Stan Hoeppner [this message]
2013-12-28 23:39 ` Arkadiusz Miśkiewicz
2013-12-29 0:54 ` Stan Hoeppner
2013-12-29 11:23 ` Arkadiusz Miśkiewicz
2013-12-29 9:50 ` Dave Chinner
2013-12-29 11:57 ` Arkadiusz Miśkiewicz
2013-12-29 23:27 ` Dave Chinner
2013-12-30 1:55 ` Stan Hoeppner
2013-12-30 11:27 ` Matthias Schniedermeyer
2013-12-30 13:19 ` Roger Willcocks
2013-12-30 16:25 ` Stan Hoeppner
2013-12-30 17:19 ` Stefan Ring
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=52BF4A47.3010604@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=jra@baylink.com \
--cc=xfs@oss.sgi.com \
/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