Using an SSD as swap?

[omegahalo-Re5JQEeQqe8AvxtiuMwx3w at public.gmane.org (Chris O'Connell)]

I would say that putting a swap file on an SSD drive is probably not a good
idea, especially if you have limited physical memory and a tons of paging
takes place.

I did a quick google and found that a few sites had the same general take on
paging to a solid state drive:
http://superuser.com/questions/51724/should-i-keep-my-swap-file-on-an-ssd-drive

<http://superuser.com/questions/51724/should-i-keep-my-swap-file-on-an-ssd-drive>
-Chris

On Thu, Dec 2, 2010 at 8:02 AM, Chris O'Connell <omegahalo-Re5JQEeQqe8AvxtiuMwx3w at public.gmane.org> wrote:

> So that being said, is using an SSD drive for a swap a good idea?
>
>
> On Thu, Dec 2, 2010 at 7:58 AM, Robert Krawitz <rlk-FrUbXkNCsVf2fBVCVOL8/A at public.gmane.org> wrote:
>
>> On Tue, 30 Nov 2010 22:46:49 -0500, Chris O'Connell wrote:
>> >>From all of my reading I've found that SSD drives have a limited number
>> of
>> > write cycles.  This limitation is the primary reason that defragging an
>> SSD
>> > drive is not recommended.
>>
>> Yup.  Of course, with no rotational and seek latencies,
>> defragmentation doesn't accomplish very much anyhow.
>>
>> > The protocol used to write to SSD drives is called TRIM.  One part
>> > of TRIM distributes the write cycles across the drive.  In fact, I
>> > believe that SSD cells are not ever erased, instead they are
>> > overwritten to prevent cell failure.
>>
>> TRIM is, I believe, a way for the host OS to tell the drive that
>> certain parts of the drive aren't in use, to enable more efficient
>> wear leveling and internal defragmentation.
>>
>> I also think it's not possible to overwrite flash.  If I remember
>> correctly, the typical organization is that there are two levels of
>> sectors: the smallest addressable unit is 512 bytes, but there's a
>> larger unit (typically something like 512K) that's the smallest that
>> can be erased.
>>
>> > Has anyone else heard this?
>>
>
>