[Xapian-discuss] Working Demo for WWW Search Engine

[Kevin SoftDev]

Olly,

Thank for the suggestion to parse the query to multiple terms. Previously I
implemented this same search engine using FullText Index in MySQL 5.0 having
almost 1 million records (web pages) size of the table was approaching 3GB.

Running on the Suse 10.0 Pentium 2.8 GHz with 2 GB memory the search started
to slow down using MySQL 5.0 where some results were coming after 10-15
seconds and the CPU usage was approaching 99% and memory usage 25%.

With Xapian I see CPU usage between 3-4% per search and memory usage only
0.3%.

Check the Xapian performance for your self. :-)
http://nitra.net/cgi-bin/hladaj.cgi?a=q&q=praha+hrad

Thanks.
Kevin Duraj





On 3/1/06, Olly Betts <olly at survex.com> wrote:
>
> On Wed, Mar 01, 2006 at 07:41:40AM -0800, Kevin SoftDev wrote:
> > It works except the city is spelled praha, prague is the english version
> > http://nitra.net/cgi-bin/hladaj.cgi?a=q&q=praha
>
> Yeah, I'm aware that's the anglicised spelling - it was just the first
> thing that came into my head to search for.  The bug I was pointing out
> was the content-type, not the lack of results.
>
> > One bug is still there that it works only with one term based on the
> > Perl demo script that came with Xapian. As soon as user type two terms
> > nothing come up. I am not sure if this is bug of Perl API or is mine.
> > [...]
> > --- two terms is called like this?
> > my $enq = $db->enquire( 'Praha Hrad' );
>
> No, that produces a one term query with a space in.  Try this:
>
> my $qp = Search::Xapian::QueryParser->new();
> # Set any options you want on $qp...
> my $enq = $db->enquire($qp->parse_query('Praha Hrad'));
>
> Cheers,
>    Olly
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.tartarus.org/pipermail/xapian-discuss/attachments/20060301/8d7326b5/attachment.htm