From: David Teller <David.Teller@univ-orleans.fr>
To: Vincent Hanquez <tab@snarc.org>
Cc: Oliver Bandel <oliver@first.in-berlin.de>, caml-list@inria.fr
Subject: Re: [Caml-list] Now it's faster (addendum to "Performance-question")
Date: Thu, 07 Feb 2008 10:55:34 +0100 [thread overview]
Message-ID: <1202378134.6444.1.camel@Blefuscu> (raw)
In-Reply-To: <20080206120403.GA5335@snarc.org>
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.
next prev parent reply other threads:[~2008-02-07 9:55 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 [this message]
2008-02-09 10:03 ` Oliver Bandel
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=1202378134.6444.1.camel@Blefuscu \
--to=david.teller@univ-orleans.fr \
--cc=caml-list@inria.fr \
--cc=oliver@first.in-berlin.de \
--cc=tab@snarc.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 NNTP newsgroup(s).