caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: c-bauer-olsbruecken@t-online.de (Christoph Bauer)
To: skaller <skaller@users.sourceforge.net>
Cc: Erik de Castro Lopo <mle+ocaml@mega-nerd.com>,
	caml-list@yquem.inria.fr, matthieu.dubuget@laposte.net
Subject: Re: [Caml-list] ANNOUNCE : libsndfile-ocaml alpha
Date: Tue, 02 Jan 2007 08:47:14 +0100	[thread overview]
Message-ID: <87hcv96fb1.fsf@elefant.olsbruecken.local> (raw)
In-Reply-To: <1167699073.13679.15.camel@rosella.wigram> (skaller@users.sourceforge.net's message of "Tue\, 02 Jan 2007 11\:51\:13 +1100")

skaller <skaller@users.sourceforge.net> writes:

> On Tue, 2007-01-02 at 06:58 +1100, Erik de Castro Lopo wrote:
>> That file
>> is:
>> 
>>     96000 * 60 * 60 * 8 * 4 bytes => 
>>     11059.200 Mbytes =>
>>     11.059 Gbytes
>> 
>> Nobody is going to load the whole of that file into memory at once. 
>
> Why not? That's tiny compared to available address space on a 64
> bit machine, and personal computers have heaps
> of free address space.

I had to deal with big files and OCaml too and Erik's approach
sound good to me. 

On 64 bit machines you may mmap huge files, but you can't on 32-bit
machines. I run in troubles with files > 700MB.  Maybe you could mmap
smaller blocks, but this isn't possible with the current
implementation of bigarrays mmap (since you need to mmap with an
offset). Furthermore mmap is a bit different on different operation
system.

Measurements show that mmap doesn't mean a big (or any) speed
up. For the OS the advantage is, that no swap space needs to be
reservered.

Christoph Bauer



  parent reply	other threads:[~2007-01-02  7:47 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-22  4:54 Erik de Castro Lopo
2006-12-27  9:32 ` [Caml-list] " Vu Ngoc San
2006-12-27 10:10   ` Erik de Castro Lopo
2006-12-27 10:42     ` Erik de Castro Lopo
2006-12-30 21:07     ` Erik de Castro Lopo
2006-12-31  3:31       ` skaller
2006-12-31  4:23         ` Erik de Castro Lopo
2006-12-31 11:08           ` Richard Jones
2006-12-31 22:51             ` Erik de Castro Lopo
2007-01-01 14:53               ` Matthieu Dubuget
2007-01-01 19:58                 ` Erik de Castro Lopo
2007-01-02  0:51                   ` skaller
2007-01-02  1:14                     ` Erik de Castro Lopo
2007-01-02  5:26                       ` Erick Tryzelaar
2007-01-02  5:39                         ` Erik de Castro Lopo
     [not found]                       ` <1167765505.5341.12.camel@rosella.wigram>
2007-01-02 22:37                         ` Erik de Castro Lopo
2007-01-02 23:46                           ` Gerd Stolpmann
2007-01-03  1:59                             ` Pal-Kristian Engstad
2007-01-03  2:49                             ` Markus Mottl
2007-01-02  7:47                     ` Christoph Bauer [this message]
2006-12-31 19:05           ` skaller
2006-12-31 22:54             ` Erik de Castro Lopo
2007-01-02 10:56       ` Vu Ngoc San
2007-01-02 11:27         ` Erik de Castro Lopo
2007-01-02 19:39           ` David Baelde
2007-01-02 23:04             ` Erik de Castro Lopo

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=87hcv96fb1.fsf@elefant.olsbruecken.local \
    --to=c-bauer-olsbruecken@t-online.de \
    --cc=caml-list@yquem.inria.fr \
    --cc=matthieu.dubuget@laposte.net \
    --cc=mle+ocaml@mega-nerd.com \
    --cc=skaller@users.sourceforge.net \
    /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).