To my experience, some customers used SAN to store the index. It's
pretty good and fast. This may be a good choice for you, but it's costly.
--
--
Chris Lu
-------------------------
Instant Scalable Full-Text Search On Any Database/Application
site: http://www.dbsight.net
demo: http://search.dbsight.com
Lucene Database Search in 3 minutes:
http://wiki.dbsight.com/index.php?title=Create_Lucene_Database_Search_in_3_minutes
DBSight customer, a shopping comparison site, (anonymous per request) got 2.6
Million Euro funding!
Andrew Bruno wrote:
Katta looks interesting. I have also been looking at SOLR, but both of
these require reworking the application, and possibly re-indexing the world
again.
Do you know if Katta supports Compass/Lucene v2.0 migration?
Also, when I say 1T, what I really mean is that we have about 1200 different
indexes, which total 1Tbyte on this server. This means that all indexes do
not need to be on one disk.
At the moment we are also processing about 20,000 index updates per hour on
the same server.
In theory SAN should work better, as its on fibre-optic so should have less
latency??? Opinions?
Thx/AB
On Thu, Feb 25, 2010 at 8:54 PM, Ian Lea <ian....@gmail.com> wrote:
We've run lucene on NAS, although not with indexes anything like as
large as 1Tb, and gave up because NFS and lucene don't really work
very well together. Google for "lucene nfs" for some details, and some
workarounds.
I'd second Kay Kay's suggestion to look at a distributed solution such as
Katta.
--
Ian.
On Wed, Feb 24, 2010 at 11:54 PM, Andrew Bruno <andrew.br...@gmail.com>
wrote:
Hello,
I am working with an application that offers its customers their own
index,
primary two indexes for different needs per customer.
As our business is growing and growing, I now have a situation where the
web
application has its customer's index on one volume, and its getting close
to
1Tbyte.
There are lots of updates and inserts, and plenty of searches. As you
can
imagine, the application is starting to slow down heavily, especially
during
high traffic time when documents (PDF, DOCs, etc) are indexed.
Since the disk IO on the server is high, our datacenter engineers
suggested
we look at NAS or SAN, for performance gain, and for future growth.
Has anyone had any experience in running Lucene2.0/Compass in these
environments? Do you know of any case studies, whitepapers, web sites?
Thanks
Andrew
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-user-h...@lucene.apache.org
