caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Oliver Bandel <oliver@first.in-berlin.de>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Now it's faster (addendum to "Performance-question")
Date: Sat,  9 Feb 2008 11:03:00 +0100	[thread overview]
Message-ID: <1202551380.47ad7a5482948@webmail.in-berlin.de> (raw)
In-Reply-To: <1202378134.6444.1.camel@Blefuscu>

Well,


I didn't say the buffer library is slow.
I said, it's much faster than using "^".

For not-that-intensive string-concat's,
2^" is fast enough, but when you do often
concat strings, then buffer-module is
faster.

Do you mean the buffer module should be made better or do you think,
the "^" operator should be implemented differently?
If Buffer-module might be even faster, when it's changed,
that's fine, but IMHO it's quite fast.

Ciao,
   Oliver

Zitat von David Teller <David.Teller@univ-orleans.fr>:

> A possible improvement of the buffer library (along with a ropes
> library) may be a good future subject for OSR. Well, once we have
> answered the already-asked questions, of course.
>
> Cheers,
>  David
>
> On Wed, 2008-02-06 at 13:04 +0100, Vincent Hanquez wrote:
> > well i'm pretty sure you could go down even further with your own
> > implementation of a buffer library.
> >
> > the buffer library is actually pretty bad since it's actually just
> a
> > simple string. each time the buffer need to grow, the string is
> > reallocated and the previous one is copied to the new string.
> > and you got the 16mb limit (max_string_length) on 32bit.
> >
> > if you implement a growing array of fixed sized string (4K for
> example),
> > you just don't need to copy data each time your buffer need to
> grow. I
> > suspect it might be even faster than the normal buffer in your case
> > (lots of data appending), but depends on what you do with your
> buffer
> > afterwards.
> >
> --
> David Teller
>  Security of Distributed Systems
>   http://www.univ-orleans.fr/lifo/Members/David.Teller
>  Angry researcher: French Universities need reforms, but the LRU act
> brings liquidations.
>
> _______________________________________________
> Caml-list mailing list. Subscription management:
> http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
> Archives: http://caml.inria.fr
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>


  reply	other threads:[~2008-02-09 10:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-06 11:33 Oliver Bandel
2008-02-06 11:55 ` [Caml-list] " Oliver Bandel
2008-02-06 12:04   ` Vincent Hanquez
2008-02-07  9:55     ` David Teller
2008-02-09 10:03       ` Oliver Bandel [this message]
2008-02-09 10:29         ` David Teller
2008-02-09 10:18     ` Oliver Bandel
2008-02-11 12:36       ` Vincent Hanquez
2008-02-11 10:01     ` Jean-Christophe Filliâtre
2008-02-11 12:41       ` Vincent Hanquez
2008-02-11 14:34         ` Jean-Christophe Filliâtre
2008-02-11 14:51           ` Vincent Hanquez

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=1202551380.47ad7a5482948@webmail.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;
as well as URLs for NNTP newsgroup(s).