unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Amirouche Boubekki <amirouche.boubekki@gmail.com>
To: Guile User <guile-user@gnu.org>
Subject: babelia
Date: Sat, 16 Nov 2019 11:06:01 +0100	[thread overview]
Message-ID: <CAL7_Mo85f11cncZOcN7V8Uc2=QRGRkK=84XvJuApNeBoLkXtVQ@mail.gmail.com> (raw)

I restarted working on my personal search engine.

It used to be called culturia [0] with too many planned features. At
some point, I called it asylum [1] and focused on personal knowledge
base aspects and the last iteration was called gotofish [2]

[0] https://framagit.org/a-guile-mind/culturia
[1] https://framagit.org/a-guile-mind/culturia.next
[2] https://git.sr.ht/~amz3/guile-gotofish

I learned much from all this projects. In particular, I learned that
it will be a long long long project, even if I focus only on "personal
search engine" line of work.

The last iteration, gotofish, was not too bad even if it has bitrot.
Based on my research and practical experiment, it seems very clear
that there is no workaround the use of map-reduce, that might be known
as n-par-for-each [3].

[3] https://www.gnu.org/software/guile/manual/html_node/Parallel-Forms.html#index-n_002dpar_002dfor_002deach

I made a prototype similar to that n-par-for-each, except it works
with guile-fibers, is asynchronous and works with a shared pool of
threads instead of spawning N threads for each incoming query like
gotofish does.

Related blog post: https://hyper.dev/blog/on-the-road-to-babelia.html

If you want to help or discuss those matters, do not hesitate to reply
to this message.


Cheers,

Amirouche ~ amz3 ~ https://hyper.dev



             reply	other threads:[~2019-11-16 10:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-16 10:06 Amirouche Boubekki [this message]
2019-11-16 10:19 ` babelia Amirouche Boubekki
2019-11-16 12:08 ` babelia Arne Babenhauserheide
2019-11-18 17:12   ` babelia Amirouche Boubekki
2019-11-22 17:38 ` babelia Amirouche Boubekki
2019-12-06 13:19 ` babelia 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='CAL7_Mo85f11cncZOcN7V8Uc2=QRGRkK=84XvJuApNeBoLkXtVQ@mail.gmail.com' \
    --to=amirouche.boubekki@gmail.com \
    --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).