lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marvin Humphrey <mar...@rectangular.com>
Subject Re: SSD Experience (on developer machine)
Date Tue, 23 Aug 2011 12:07:48 GMT
On Tue, Aug 23, 2011 at 01:37:06PM +0200, Toke Eskildsen wrote:
> Yes, the first generation of SSDs had bad wear-leveling and there has
> been some exceptionally bad eggs along the way, but we're long past that
> point now. All brand name SSDs use wear leveling and unless you set up
> pathological destruction cases (fill the drive to 99% and keep
> re-writing the last 1% ) the drive will be obsolete before it wears out.
> 
> What kills modern SSDs are either non-rewrite-related errors or server
> use that requires a full to-hardware flushes after all small changes.

I'm a little confused.  What do you mean by a "full to-hardware flush" and how
is that different from the sync()/fsync() calls that Lucene makes by default
on each IndexWriter commit()?  

Marvin Humphrey


---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org


Mime
View raw message