comment on

Dear Brethren,

do you find SuperSearch slow and unwieldy? That's because the database search is slow. I recently was playing with the most excellent KinoSearch library and discovered that certain things lend themselves well to a full-text search. For instance, I have created an index for searching CPAN's bug database (rt.cpan.org) and a web application to search it. I believe the result speaks for itself.

I am willing to dedicate time to indexing the perlmonks database (just need a place to host it). There are only about 600,000 nodes with a small number of them changing every day; at work, I used KinoSearch to index millions of documents and the searches are very fast and relevant. I believe that this is the type of thing that will a) make searching easier and b) take some load off the database.

Let's discuss? I hope I get the opportunity to contribute to the Monastery.

- Dmitri.

Update: Track the progress here: http://code.google.com/p/monk-search/

In reply to Running SuperSearch off a fast full-text index. by dmitri

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Don't ask to ask, just ask
	PerlMonks