This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Hi, I'm using Lightspeed 3.11 with Lucene.net and have a few comments/problems: 1. LS uses an old version of Lucene.net. 2. The Lucene MergeFactor parameter is not configurable - using the LuceneSearchEngine.cs from the mindscape blog and doing indexWriter.SetMergeFactor(100) instead of .SMF(10) in the CreateIndexWriter method decreases the running time of LightSpeedContext.SearchEngine.Rebuild() to 1/4th in my test case. 3. When doing a .SaveChanges to a UnitOfWork with many queued INSERTS each .Add() to the Lucene engine is done outside a BeginBulkAdd/EndBulkAdd "scope". This also causes (big) performance problems. Any hope of getting this fixed in the nightlies? :) Kind regards, Bjørn M |
|
|
Hi Bjørn, Thanks for the feedback. 1. I'll look at upgrading to a newer release of Lucene.net. I've added this to the backlog. 2. We won't be adding configuration for this via the context, but I will extend the Lucene provider to allow you to set it if using the Lucene provider that we include by default. I also think it would be smart to increase the default to 100, as the memory weight of 100 documents over 10 is fairly negligible. 3. I'll investigate this and report back. With regards to point 1 and 2, you should be able to create your own lucene provider against the newer version and expose a property for the merge factor yourself if they are blockers (as you mentioned, you've nailed number 2 already :-). I'll keep you posted and thank you for the feedback, John-Daniel |
|
|
Hello, I was wondering if it still makes sense to work with Lucene in combination with Lightspeed today? I see LightSpeed is still targeting Lucene 2. Is the speed benefit of indexing with Lucene still there? I have a product table with approx. 50000 products. Are there any plans to update LightSpeed to work with a newer Lucene? I see Lucene.NET 3.0.3 is the latest version. https://www.nuget.org/packages/Lucene.Net I already found the LuceneSearchEngine.cs from the forum/blog, so I could rewrite it to work with Lucene.NET 3.0.3. http://www.mindscapehq.com/blog/index.php/2009/02/25/lightspeed-writing-a-custom-search-engine/ Thanks, Luuk |
|
|
This afternoon, I created a new LuceneNet3SearchEngine class to work with Lucene.NET 3.0.3. For me it seems to work perfectly, but use at own risk! No warranty ;) Best regards, Luuk Kuiper The Netherlands |
|