[LUCENENET-630] Identify/Fix Bottlenecks

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Lucene.Net 4.8.0
• Component/s: Lucene.Net Core, Lucene.Net.Analysis.Common, Lucene.Net.Classification, Lucene.Net.Codecs, Lucene.Net.Expressions, Lucene.Net.Facet, Lucene.Net.Highlighter, Lucene.Net.QueryParser, Lucene.Net.Suggest
• Labels: up-for-grabs
• Assignee: Unassigned
• Reporter: Shad Storhaug
• Created: 10/Oct/19 19:25
• Updated: 09/Dec/21 17:50
• Resolved: 09/Dec/21 17:50

Description

We need some help profiling Lucene.NET to identify and/or fix any potential bottlenecks. Please make us aware of anything you find by opening a new JIRA issue or by letting us know on the dev mailing list.

Issue Links

• contains: LUCENENET-640 Sequential IndexWriter performance in concurrent environments.
• contains: LUCENENET-610 Reduce locking in FieldCacheImpl::Cache::Get
• contains: LUCENENET-644 The design and implementation of a better ThreadLocal<T>
• contains: LUCENENET-629 Lucene & Memory Mapped Files
• contains: LUCENENET-643 NIOFSDirectory performance can be improved
• contains: LUCENENET-642 Eliminate Runtime Reflection Code from TokenStream