From: amirouche <amirouche@hypermove.net>
To: guile-user@gnu.org
Subject: Re: [HELP] a search engine in GNU Guile
Date: Fri, 10 Feb 2017 11:56:24 +0100 [thread overview]
Message-ID: <4032f9c1-1d63-b3d5-6cf5-0595e51b3acb@hypermove.net> (raw)
In-Reply-To: <ba0ca9bafafabe3aa8d4226629a71454@hypermove.net>
Héllo Ralf,
On 09/09/2016 20:10, Amirouche Boubekki wrote:
> On 2016-09-09 16:05, Ralf Mattes wrote:
>> On Fri, Sep 09, 2016 at 09:39:24AM -0500, Christopher Allan Webber wrote:
>>> Amirouche Boubekki writes:
[...]
>> (and, in the case of Lucene, a rather well working,
>
> It's not possible to use a custom storage engine with Lucene.
>
>> extremly mature
>
> My theory is that some search engine businesses like algolia forked
> Lucene to build
> it on top of something similar to wiredtiger and can now claim
> impressive performance.
Based on the blog post serie algolia has done, they do not use
something like wiredtiger. So I was fully wrong. They have fine
tuned datastructures for every problem they encounter for indexing
and querying.
https://blog.algolia.com/inside-the-algolia-engine-part-1-indexing-vs-search/
Anyway, outside the far reaching goal of achieving concept search,
I find wiredtiger handy+good enough that's why I use it. That's said
if I need to get a living from my free coding I will not use
wiredtiger.
Best regards,
Amirouche
next prev parent reply other threads:[~2017-02-10 10:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-13 15:25 [HELP] a search engine in GNU Guile Amirouche Boubekki
2016-09-04 13:35 ` Amirouche Boubekki
2016-09-09 14:40 ` Christopher Allan Webber
2016-09-10 6:33 ` Amirouche Boubekki
2016-09-09 14:39 ` Christopher Allan Webber
2016-09-09 14:05 ` Ralf Mattes
2016-09-09 18:10 ` Amirouche Boubekki
2017-02-10 10:56 ` amirouche [this message]
2016-09-23 5:52 ` Amirouche Boubekki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4032f9c1-1d63-b3d5-6cf5-0595e51b3acb@hypermove.net \
--to=amirouche@hypermove.net \
--cc=guile-user@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).