Maybe spend some time playing with Compass rather than speculating ;) If it helps, on the project where I last used compass, we had what I consider to be a small dataset - just a few million documents. Nothing related to indexing/searching took more than a second or 2 - mostly it was 10's or 100's of milliseconds. That app has been live almost 3 years.
Correct, compass does not implement sharding, etc - but I thought we already established that. Anyway, we have strayed well off the point of the original question .... so lets leave it at that. -N -----Original Message----- From: Fuad Efendi [mailto:f...@efendi.ca] Sent: 25 January 2010 16:46 To: solr-user@lucene.apache.org Subject: RE: Solr vs. Compass > >> Even if "commit" takes 20 minutes? > I've never seen a commit take 20 minutes... (anything taking that long > is broken, perhaps in concept) "index merge" can take from few minutes to few hours. That's why nothing can beat SOLR Master/Slave and sharding for huge datasets. And reopening of IndexReader after each commit may take at least few seconds (although depends on usage patterns). "IndexReader or IndexSearcher will only see the index as of the "point in time" that it was opened. Any changes committed to the index after the reader was opened are not visible until the reader is re-opened." I am wondering how Compass opens new instance of IndexReader (after each commit!) - is it really implemented? I can't believe! It will work probably fine for small datasets (less than 100k), and 1 TPD (transaction-per-day)... Very expensive and unnatural ACID... -Fuad =============================================================================== Please access the attached hyperlink for an important electronic communications disclaimer: http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html ===============================================================================
