From: Joel Reicher <joel.reicher@gmail.com>
To: Help GNU Emacs <help-gnu-emacs@gnu.org>
Subject: Re: Which Elisp data structure is fastest for searching?
Date: Fri, 27 Dec 2024 10:03:57 +1100 [thread overview]
Message-ID: <86bjwycahu.fsf@gmail.com> (raw)
In-Reply-To: <Z20ZksL7H4P0tRA0@lco2> (Jean Louis's message of "Thu, 26 Dec 2024 11:53:38 +0300")
Jean Louis <bugs@gnu.support> writes:
[...]
> 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
This makes me think you don't yet know what your equality
predicate is, and whether your search space is totally or
partially ordered, or unordered.
I don't think you will be able to choose a data structure until
you have these things figured out.
> - there will be different hash with accurate information about
> the ID,
> such as title, URL, description
I am not sure you are using the word "hash" the same way "hash
table" does, but if I'm right about the above, it doesn't matter,
because you must figure those things out first.
> 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.
Yes it can, but I think worrying about that now is a bit like
worrying about how long to age the cheese when you haven't even
milked the cow.
Regards,
- Joel
next prev parent reply other threads:[~2024-12-26 23:03 UTC|newest]
Thread overview: 7+ 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
2024-12-26 9:23 ` tomas
2024-12-26 11:49 ` Jean Louis
2024-12-26 23:03 ` Joel Reicher [this message]
2024-12-27 11:16 ` Jean Louis
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=86bjwycahu.fsf@gmail.com \
--to=joel.reicher@gmail.com \
--cc=help-gnu-emacs@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).