Re: SSD Experience (on developer machine)

On Wed, 2011-08-24 at 11:46 +0200, David Nemeskey wrote: > Theoretically, in the case described above, it would be possible to move > 'static' data (data of cells that have not been written to for a long time) > to > the 5GB in question and use the 'fresher' cells as free space; this could be >

Re: SSD Experience (on developer machine)

On Wed, 2011-08-24 at 13:42 +0200, Federico Fissore wrote: > I add a question. Toke you said that "the current state of wear can be > queried". How? With a S.M.A.R.T.-tool, preferably up-to-date to get it to display the vendor-specific properties in an easy to understand manner. On my Ubuntu-box

Re: SSD Experience (on developer machine)

>> we are probably running out of topic here, but for the record, there is >> also someone lamenting about ssd > I find all of this highly on-topic. SSD reliability is an important > issue. We use customer-grade SSDs (Intel 510 were the latest ones > bought) in our servers as we see no point in en

Re: SSD Experience (on developer machine)

David Nemeskey, il 24/08/2011 11:46, ha scritto: [...] Theoretically, in the case described above, it would be possible to move 'static' data (data of cells that have not been written to for a long time) to the 5GB in question and use the 'fresher' cells as free space; this could be done in a rou

Re: SSD Experience (on developer machine)

Hi, interesting discussion about SSDs. On 2011 August 23, Tuesday 20:56:44 Toke Eskildsen wrote: > > 50TB before _every single cell in the drive_ gives up. You will change > > the drive much sooner, probably at the first two occasions of corrupted > > data. > > 50TB for the 5GB of cells. The res

Re: SSD Experience (on developer machine)

Sorry Toke, I do not know. The service shop replaced it fairly blindly. paul Le 23 août 2011 à 20:46, Toke Eskildsen a écrit : > On Tue, 2011-08-23 at 17:20 +0200, Paul Libbrecht wrote: >> Funnily, I had such an experience: an SSD on the laptop of the brand >> SanDisk, guaranteed for 80 TB of

Re: SSD Experience (on developer machine)

On Tue, 2011-08-23 at 17:56 +0200, Federico Fissore wrote: > Great reply, thank you. Will re-read it and re-evaluate my position Thanks for having an open mind. Toke: > > Let's say you have a drive with just 5GB left. Let's say that the cells > > can handle 10,000 writes. Doing constant rewrites

Re: SSD Experience (on developer machine)

On Tue, 2011-08-23 at 17:20 +0200, Paul Libbrecht wrote: > Funnily, I had such an experience: an SSD on the laptop of the brand SanDisk, > guaranteed for 80 TB of writes. > Well, I had it twice changed under guarantee. Then the shop provided me an > OCZ. > Maybe that lasts longer... I'm still in

Re: SSD Experience (on developer machine)

Great reply, thank you. Will re-read it and re-evaluate my position Just one comment Toke Eskildsen, il 23/08/2011 17:11, ha scritto: [...] Let's say you have a drive with just 5GB left. Let's say that the cells can handle 10,000 writes. Doing constant rewrites of the 5GB gives you 10,000 * 5G

Re: SSD Experience (on developer machine)

Funnily, I had such an experience: an SSD on the laptop of the brand SanDisk, guaranteed for 80 TB of writes. Well, I had it twice changed under guarantee. Then the shop provided me an OCZ. Maybe that lasts longer... I'm still in guarantee. paul Le 23 août 2011 à 17:11, Toke Eskildsen a écrit :

Re: SSD Experience (on developer machine)

On Tue, 2011-08-23 at 16:10 +0200, Federico Fissore wrote: [Toke: Re-writes is not a problem now] > Maybe this still is a point, thinking at how easy is today to fill your > local storage: for example, a "common" user will store video files. It is only a problem if the SSD is stored to the brim

Re: SSD Experience (on developer machine)

Toke Eskildsen, il 23/08/2011 13:37, ha scritto: [...] 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 cas

Re: SSD Experience (on developer machine)

On Tue, 2011-08-23 at 14:07 +0200, Marvin Humphrey wrote: > 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()? A standard flush from the operating system flu

Re: SSD Experience (on developer machine)

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

Re: SSD Experience (on developer machine)

On Tue, 2011-08-23 at 11:52 +0200, Federico Fissore wrote: > we are probably running out of topic here, but for the record, there is > also someone lamenting about ssd I find all of this highly on-topic. SSD reliability is an important issue. We use customer-grade SSDs (Intel 510 were the latest

Re: SSD Experience (on developer machine)

we are probably running out of topic here, but for the record, there is also someone lamenting about ssd http://www.codinghorror.com/blog/2011/05/the-hot-crazy-solid-state-drive-scale.html the underlying point is correct: SSD offer much less re-writes of the same "sector" than disk based so,

Re: SSD Experience

I think we're getting out of topic about Lucene usage for SSDs but I fully acknowledge that below mail: SSDs are faster than normal disk for development. Actually, one of the things that got real faster with the SSD is IntelliJ indexing and reboot; I could not tell if it is using Lucene sadly. I

Re: SSD Experience

> > > We installed SSDs in all developer machines in 2009 (Intel X25) and > haven't looked back. > > I can confirm this from my own experience. Once you have a (fast) SSD on your development machine you are not likely to go back to a spinning drive... Dawid

Re: SSD Experience

On Tue, 2011-08-23 at 10:23 +0200, Dawid Weiss wrote: > This one is humorous (watch for foul language though). It does get to > the point, however, and Bergman is a clever guy: > http://www.livestream.com/oreillyconfs/video?clipId=pla_3beec3a2-54f5-4a19-8aaf-35a839b6ecaa We installed SSDs in all

Re: SSD Experience

This one is humorous (watch for foul language though). It does get to the point, however, and Bergman is a clever guy: http://www.livestream.com/oreillyconfs/video?clipId=pla_3beec3a2-54f5-4a19-8aaf-35a839b6ecaa Dawid On Tue, Aug 23, 2011 at 10:00 AM, Toke Eskildsen wrote: > On Mon, 2011-08-22

Re: SSD Experience

On Mon, 2011-08-22 at 18:49 +0200, Rich Cariens wrote: > Does anyone have any experiences or stories they can share about how SSDs > impacted search performance for better or worse? Our measurements are getting old, but since spinning disks hasn't improved and SSDs has improved substantially since

Re: SSD Experience

22 aug 2011 kl. 18.49 skrev Rich Cariens: > I found a Lucene SSD performance benchmark > docbut > the wiki engine is refusing to let me view the attachment (I get "You > are not allowed to d

SSD Experience

(Cross-posted from solr-users) Ahoy ahoy! Does anyone have any experiences or stories they can share about how SSDs impacted search performance for better or worse? I found a Lucene SSD performance benchmark doc