From: Jean Louis <bugs@gnu.support>
To: Joel Reicher <joel.reicher@gmail.com>
Cc: Help GNU Emacs <help-gnu-emacs@gnu.org>
Subject: Re: Which Elisp data structure is fastest for searching?
Date: Thu, 26 Dec 2024 11:53:38 +0300 [thread overview]
Message-ID: <Z20ZksL7H4P0tRA0@lco2> (raw)
In-Reply-To: <86wmfnc66h.fsf@gmail.com>
* Joel Reicher <joel.reicher@gmail.com> [2024-12-26 09:25]:
> > A hash table is a very fast kind of lookup table, somewhat like an alist
> > (*note Association Lists::) in that it maps keys to corresponding
> > values.
> >
> > The above is not so conclusive and I have not done measurements.
> >
> > It says "somewhat like an alist", but is the alist faster in searching
> > through elements or the hash table?
>
> It depends on the kind of search you are doing. As an extreme example,
> imagine your search was not based on the hash table key; you might have to
> go through every entry in the table to find what you're looking for.
>
> This is why different data structures exist. There is no "best"; only "best
> for..."
As is written in manual that hash table is very fast, I believe yes,
though my search may not be.
I will use following approach:
- there will be list or hash with values that are to be searched,
those values will have their ID, that information will be prepared
for easier searching, like special symbols removed, only words
remaining, maybe even small words could be removed
- there will be different hash with accurate information about the ID,
such as title, URL, description
That is approach I know. Then I can give relevant information for
website search.
I wonder if Emacs can remain in memory keeping to answer HTTP
requests, so that I do not load it every time.
--
Jean Louis
next prev parent reply other threads:[~2024-12-26 8:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-25 9:33 Which Elisp data structure is fastest for searching? Jean Louis
2024-12-26 6:24 ` Joel Reicher
2024-12-26 8:53 ` Jean Louis [this message]
2024-12-26 9:23 ` tomas
2024-12-26 11:49 ` Jean Louis
2024-12-26 23:03 ` Joel Reicher
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Z20ZksL7H4P0tRA0@lco2 \
--to=bugs@gnu.support \
--cc=help-gnu-emacs@gnu.org \
--cc=joel.reicher@gmail.com \
/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).