Optimal way to search about contain text in million of records.

Question

1.00/5 (1 vote)

See more:

I used indexing throw Lucene.net, but the max time that lucene.net can give you the result is 6 minute.
My website based on the search performance, i need another strategy or methodology to using them.
If someone know another way else (lucene.net) to search about text in million of records.

Thank you

Posted 22-Sep-12 2:37am

aodeh

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Christiaan Rakowski · Answer 1 · 2012-09-22T02:54:00

If the text records are in a database using the database manager's build in search functionality will probably be a lot faster. After all, that is what is build for.

If you read the text from files on the hard disk it might be your implementation. I am not familiar with Lucene and how it works, but if it looks through those files each query there is a lot of overhead in opening and closing the files each time.

I personally once wrote a search system that indexed txt files, but since the number of them was quite small, as was the amount of content, I just read the file as one long string and dumped it into SQLServer. Performance was very well, but I don't think this will be the most optimal strategy if you have 1M PDFs to index.

if you could you go into some more detail of the system: where does the text come from, where is it stored, how much text is in each record, that sort of thing, we might be able to provide some better, more directly usable, advice.