Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: pass (nike.apache.org: domain of luocan19826164@sohu.com
 designates 61.135.132.86 as permitted sender)
From: "luocanrao" <luocan19826164@sohu.com>
To: <java-user@lucene.apache.org>
Subject: A question bout google search index?
Date: Wed, 9 Jun 2010 22:18:17 +0800
Message-ID: <027401cb07de$a3c6a5b0$eb53f110$@com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0275_01CB0821.B1E9E5B0"
Thread-Index: AcsH3psaygUGspxZRaO6hGQpvLtl3Q==
Content-Language: zh-cn

------=_NextPart_000_0275_01CB0821.B1E9E5B0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

A news bout google search index. Index system of Lucene can also support
realtime search, 

Is there some difference between them?

 
With Caffeine, we analyze the web in small portions and update our search
index on a continuous basis, globally. As we find new pages, or new
information on existing pages, we can add these straight to the index. That
means you can find fresher information than ever before-no matter when or
where it was published.

 
Caffeine lets us index web pages on an enormous scale. In fact, every second
Caffeine processes hundreds of thousands of pages in parallel. If this were
a pile of paper it would grow three miles taller every second. Caffeine
takes up nearly 100 million gigabytes of storage in one database and adds
new information at a rate of hundreds of thousands of gigabytes per day. You
would need 625,000 of the largest iPods to store that much information; if
these were stacked end-to-end they would go for more than 40 miles


------=_NextPart_000_0275_01CB0821.B1E9E5B0--