From: Oliver Bandel <oliver@first.in-berlin.de>
To: caml-list@inria.fr
Subject: Re: [Caml-list] mboxlib reloaded ;-)
Date: Sat, 28 Apr 2007 01:12:20 +0200 [thread overview]
Message-ID: <20070427231220.GA1507@first.in-berlin.de> (raw)
In-Reply-To: <20070427162911.GA10099@furbychan.cocan.org>
Hi,
only a short note, because I tonight will not explore it in detail...
On Fri, Apr 27, 2007 at 05:29:11PM +0100, Richard Jones wrote:
> On Fri, Apr 27, 2007 at 03:54:25PM +0200, Oliver Bandel wrote:
> > Hello,
> >
> > after two years of doing nothing on it,
> > I today found my mboxlib, I started to
> > write in 2005.
> >
> > I have put the mli-file on the web and
> > maybe the library itself will follow
> > during the next time.
> >
> > Any feedback, questions and suggestions are welcome.
> >
> > http://me.in-berlin.de/~first/software/libraries/mboxlib/
>
> The source for COCANWIKI[1] contains extensive support for threading
> of mail messages, based on JWZ's algorithm:
>
> http://www.jwz.org/doc/threading.html
Nice... you speak of an optimized algorithm for threading.
I didn't explored your solution nor did I explored your
paper in detail (tomorrow I think I have the time to do it),
but IMHO the best thing for handling message-threads
is to use tries-datastructure with messgae-id's
as identifers (instead of char's, as they are used normally).
So: did you reimplemented the tries-datastructure
as abstraction on message ID's, or did you
made it different?
>
> You are of course welcome to copy this. If there are any license
> issues let me know & I can fix them.
>
> I'd also like to point you to another useful JWZ doc:
>
> http://www.jwz.org/doc/mailsum.html
Well, the same here: tomorrow I can look at itin more detail;
but the problem of fast mbox-usage I today also found out as
a problem, as I first time used a test-mbox of about 100 MB.
Normally I would use some MB's of size, because I think
ths is the normal size; but I had some dscussions on the
berlin Linux user group, and some people were anbnoyed that
mutt needs some seconds to read in mbox-files of about
80 MB's.
So, I then checked my mboxlib and saw that it is quite slow,
compared to what I expected ( expect! I did not tried it
on my development machine because I have nomutt installed there)
and even if native-code smuch faster, it's nevertheless slow...
...so I thought I have to redesign my scanner-stage.
(I use Str-module and ocamnllex mixed together; maybe
using a plain selfwritten OCaml-scanner might be better here).
Ciao,
Oliver
P.S.: 12 seconds for 100 MB seems tobe quite slow...
I very often call the lexer, and that might be done
smarter.
Maybe your pages will show some useful attempts.
next prev parent reply other threads:[~2007-04-27 23:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-27 13:54 Oliver Bandel
2007-04-27 16:29 ` [Caml-list] " Richard Jones
2007-04-27 23:12 ` Oliver Bandel [this message]
2007-04-28 0:54 ` skaller
2007-04-28 10:47 ` Oliver Bandel
2007-04-28 10:54 ` Gabriel Kerneis
2007-04-28 11:44 ` Oliver Bandel
2007-04-28 13:49 ` skaller
2007-04-28 14:18 ` Oliver Bandel
2007-04-29 10:45 ` Richard Jones
2007-04-29 15:41 ` Oliver Bandel
2007-04-29 18:51 ` Robert Roessler
2007-05-01 11:00 ` camomile-problem (Re: [Caml-list] mboxlib reloaded ;-)) Oliver Bandel
2007-05-01 10:56 ` [Caml-list] mboxlib reloaded ;-) Oliver Bandel
2007-04-28 7:56 ` Richard Jones
2007-04-28 10:58 ` Oliver Bandel
[not found] ` <20070429103911.GA30510@furbychan.cocan.org>
2007-04-29 15:43 ` Oliver Bandel
2007-09-24 18:22 ` ocamllex speed [was Re: [Caml-list] mboxlib reloaded ;-)] Bruno De Fraine
2007-09-24 19:54 ` Alain Frisch
2007-09-25 8:53 ` Bruno De Fraine
2007-09-24 22:06 ` skaller
2007-09-27 5:26 ` Chris King
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070427231220.GA1507@first.in-berlin.de \
--to=oliver@first.in-berlin.de \
--cc=caml-list@inria.fr \
/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