caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Will M. Farr" <farr@MIT.EDU>
To: skaller@users.sourceforge.net
Cc: "O'Caml Mailing List" <caml-list@inria.fr>,
	Christophe TROESTLER <Christophe.Troestler@umh.ac.be>
Subject: Re: [Caml-list] [Benchmark] NBody
Date: Mon, 7 Feb 2005 20:48:16 -0500	[thread overview]
Message-ID: <80eb59bd970cd828d562f79e8eb565bf@mit.edu> (raw)
In-Reply-To: <1107826151.13571.199.camel@pelican.wigram>

Doesn't caml store records whose types are all floats as a float array 
anyway?  I thought I remembered this optimization going by in the 
manual somewhere.

Will


On 7 Feb 2005, at 8:29 PM, skaller wrote:

> On Tue, 2005-02-08 at 05:57, Christophe TROESTLER wrote:
>
>
>> type planet = {
>>   mutable x : float;  mutable y : float;  mutable z : float;
>>   mutable vx: float;  mutable vy: float;  mutable vz: float;
>>   mass : float;
>> }
>
> Advice from old FORTRAN hacker:
>
> This is a bad data structure for Ocaml.
>
> Try using an unboxed float array of 7 times the length instead,
> this will eliminate boxing, eliminate write barriers,
> eliminate garbage collection, reduce memory requirements.
>
>
> -- 
> John Skaller, mailto:skaller@users.sf.net
> voice: 061-2-9660-0850,
> snail: PO BOX 401 Glebe NSW 2037 Australia
> Checkout the Felix programming language http://felix.sf.net
>
>
>
> _______________________________________________
> 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:[~2005-02-08  1:48 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-07 18:57 Christophe TROESTLER
2005-02-07 19:16 ` [Caml-list] " Will M. Farr
2005-02-07 19:36   ` Christophe TROESTLER
2005-02-07 19:55     ` Will M. Farr
2005-02-08 10:34       ` Olivier Andrieu
2005-02-08 10:52         ` Micha
2005-02-07 20:16     ` Markus Mottl
2005-02-07 19:37 ` Martin Jambon
2005-02-07 19:46   ` Christophe TROESTLER
2005-02-07 20:22     ` Martin Jambon
2005-02-07 20:04   ` sejourne_kevin
2005-02-07 20:32     ` Robert Roessler
2005-02-07 22:57     ` Oliver Bandel
2005-02-08  1:29 ` skaller
2005-02-08  1:48   ` Will M. Farr [this message]
2005-02-08  9:01     ` Ville-Pertti Keinonen
2005-02-08  9:37     ` skaller
2005-02-08 10:10       ` Ville-Pertti Keinonen
2005-02-08 16:36         ` skaller
2005-02-08 12:04       ` Marcin 'Qrczak' Kowalczyk
2005-02-08 17:06         ` skaller
2005-02-08 10:25   ` Xavier Leroy
2005-02-08 18:34     ` skaller
2005-02-08 10:43 ` Xavier Leroy
2005-02-08 11:26   ` Ville-Pertti Keinonen
2005-02-08 15:59   ` Florian Hars
2005-02-13 16:40   ` Christoph Bauer
2005-02-13 18:13   ` Christophe TROESTLER
2005-02-24 22:18   ` NBody (one more question) Christophe TROESTLER
2005-02-25 17:06     ` [Caml-list] " John Carr
2005-02-25 17:17       ` Christophe TROESTLER
2005-02-26 16:08         ` John Carr
2005-02-25 17:24     ` Ken Rose
2005-02-25 17:42       ` Oliver Bandel
2005-02-25 17:57     ` Xavier Leroy

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=80eb59bd970cd828d562f79e8eb565bf@mit.edu \
    --to=farr@mit.edu \
    --cc=Christophe.Troestler@umh.ac.be \
    --cc=caml-list@inria.fr \
    --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).