lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shad Storhaug (Jira)" <>
Subject [jira] [Commented] (LUCENENET-647) Performance decreasement migrating from 3.0.3 to 4.8.0
Date Mon, 09 Mar 2020 08:43:00 GMT


Shad Storhaug commented on LUCENENET-647:

Thanks for the report.

However, without more information there isn't much we can do on our end. Specifically, what
is slow? Searching, indexing, analyzing?

Without seeing some code, it is hard to put together any advice on what to do about it. Could
you please provide a sample configuration that runs fast in Lucene.NET 3.0.3 and is measurably
slower when running with Lucene.NET 4.8.0?

Also, can you please confirm you are using 4.8.0-beta00007? It has several performance improvements
over the previous betas.

[~eladmarg] - Yes, there are some additional performance improvements in the trunk that haven't
been released yet. Most of them only apply to very specific configurations, though. I am hoping
to eliminate the "Support" namespace on ICU4N before doing that release.

> Performance decreasement migrating from 3.0.3 to 4.8.0
> ------------------------------------------------------
>                 Key: LUCENENET-647
>                 URL:
>             Project: Lucene.Net
>          Issue Type: Improvement
>         Environment: OS: Windows 10
> CPU: Intel Core i7-8700 
> RAM: 32Gb
>            Reporter: Mo Dje
>            Priority: Major
> Hello,
> I'm currently migrating a project, that uses Lucene.Net, from .Net Framework to .Net
> I had to migrate from 3.0.3 version of Lucene to 4.8.0 (beta0007) but I noticed performance
decreasement while measuring response time while requesting the database. The response time
using Lucene 4.8.0 is two to three times higher than 3.0.3 version.
> I read some forum topics where other users noticed this performance decreasement too.
Are you aware about that? Do you plan to do something to improve performances of Lucene 4.8.0?
> Best regards

This message was sent by Atlassian Jira

View raw message