unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Ian Price <ianprice90@googlemail.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: vhash speed thread safeness
Date: Tue, 29 Oct 2013 18:50:35 +0000	[thread overview]
Message-ID: <87ob67ykqs.fsf@Kagami.home> (raw)
In-Reply-To: <87zjpsnerz.fsf@gnu.org> ("Ludovic \=\?iso-8859-1\?Q\?Court\=E8s\?\= \=\?iso-8859-1\?Q\?\=22's\?\= message of "Tue, 29 Oct 2013 18:54:56 +0100")

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=iso-2022-jp-2, Size: 1044 bytes --]

ludo@gnu.org (Ludovic Court^[$(D+2^[(Bs) writes:

> I wonder if there^[$B!G^[(Bs some other data structure with similar properties
> that doesn^[$B!G^[(Bt have the thread-safety issue.  Maybe Ian has an idea?

HAMTs (another Bagwell creation) might be a reasonable option, but I
don't have a complete implementation. I ran into some issues with it a
while back, but I have completely forgotten what it was. I do want them
in pfds, so I guess I could take this as the kick-up-the-arse to finish
it.

> The weight-balanced trees in MIT/GNU Scheme look interesting:
>
>   http://www.gnu.org/software/mit-scheme/documentation/mit-scheme-ref/Weight_002dBalanced-Trees.html

I have those in pfds under the name bbtrees (for balanced binary
trees). They are pretty flexible, and you get reasonable times for a lot
of operations, but like a lot of tree structures not particularly cache
friendly.

-- 
Ian Price -- shift-reset.com

"Programming is like pinball. The reward for doing it well is
the opportunity to do it again" - from "The Wizardy Compiled"



  reply	other threads:[~2013-10-29 18:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-18 16:21 vhash speed thread safeness Stefan Israelsson Tampe
2013-10-29 12:34 ` Ludovic Courtès
2013-10-29 14:21   ` Stefan Israelsson Tampe
2013-10-29 17:54     ` Ludovic Courtès
2013-10-29 18:50       ` Ian Price [this message]
2014-03-24 20:59 ` Andy Wingo

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=87ob67ykqs.fsf@Kagami.home \
    --to=ianprice90@googlemail.com \
    --cc=guile-devel@gnu.org \
    --cc=ludo@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).