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
hi all
I am interested in vertical crawler. But it seems this project is not
very active. It's last update time is 11/16/2009
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
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
>
>
> 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
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
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,
You should ask on the Droids list but there's some activity in Jira. And did
you consider Apache Nutch?
On Tuesday 23 August 2011 10:17:50 Li Li wrote:
> hi all
> I am interested in vertical crawler. But it seems this project is not
> very active. It's last update time is 11/16/2009
---
It's also worth looking at ManifoldCF.
Karl
-Original Message-
From: ext Markus Jelsma
Sent: 23/08/2011, 6:24 AM
To: solr-u...@lucene.apache.org
Cc: java-user@lucene.apache.org
Subject: Re: what's the status of droids
project(http://incubator.apache.org/droids/)?
You should ask on the
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
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
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
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
Dear friends
hi
I want to use Lucene to calculate Precision and Recall.
I did these steps:
* 1*- made some index files. to do this I used indexer code and indexed txt
files which exist in this path "C:/inn" (there are 4 txt files in this
folder) and take them in "outt" folder by setting the indexp
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
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 :
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
Dear friends
hi
I want to use Lucene to calculate Precision and Recall.
I did these steps:
1- made some index files. to do this I used indexer code and indexed txt
files which exist in this path "C:/inn" (there are 4 txt files in this
folder) and take them in "outt" folder by setting the indexpath
Hmm... this looks like a side-effect of LUCENE-2680, which was merged
back from trunk to 3.1.
So the problem is, IW recycles the RAM it has allocated, and so this
method is returning the allocated RAM, even if those buffers are not
in fact in use right now (ie, filled with postings data). I think
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
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
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
I have an application using Hibernate Search 3.1.1-GA with Lucene 2.4.1 (via
lucene-snowball-2.4.1.jar ) on the backend.
Our query terms have gotten fairly lengthy (but not complex), consisting of
queries such as
* "FOOBAR TERM" AND NOT (FOOBAZ OR FOOBLA OR JUNK)*
We've gone up to queries of
On Wed, Aug 24, 2011 at 4:45 AM, Michael McCandless
wrote:
> Hmm... this looks like a side-effect of LUCENE-2680, which was merged
> back from trunk to 3.1.
>
> So the problem is, IW recycles the RAM it has allocated, and so this
> method is returning the allocated RAM, even if those buffers are n
24 matches
Mail list logo
