From: Eray Ozkural <exa@kablonet.com.tr>
To: Brian Hurt <brian.hurt@qlogic.com>
Cc: OCaml List <caml-list@inria.fr>
Subject: Re: [Caml-list] Looking for a real array
Date: Mon, 28 Apr 2003 21:29:27 +0300 [thread overview]
Message-ID: <200304282129.27582.exa@kablonet.com.tr> (raw)
In-Reply-To: <Pine.LNX.4.33.0304281123140.3160-100000@eagle.ancor.com>
Hi Brian,
On Monday 28 April 2003 19:40, Brian Hurt wrote:
> Having a reference in addition to the data structure is a little bit of
> overhead. But optimization is a tricky thing- often times, what you gain
> in the straights you lose in the curves. For example, what happens when
> some other peice of code keeps a pointer to a single element of the array,
> when the pointer to the rest of the array- and all the other elements- are
> gone? In ocaml, the array and all the other elements become garbage, and
> the last, lone object that is not garbage stays around. Also, copying
> becomes a big issue in my experience.
>
I will happily agree that asymptotic complexity is more important than
constant gains and that there are other book-keeping tasks that might make
the programming more complex than necessary.
> Personally, I find one extra level of dereferencing isn't that big of a
> deal. If you're too the point where it is a big deal, you are already
> talking about hand-tuned assembly language. My advice: stop worrying
> about minutia. Permature optimization is the root of all evil.
Yes, I'm coming from the land of evil optimizers. :) I spent a large portion
of my youth hand-optimizing 68k assembly! I was really shocked when I found
out about 2 years ago that some FORTRAN compilers could do the tricks I spent
hours on the Amiga to perform!
To be serious, I was concerned about this fact because I have, if you recall,
started writing a graph library. Unfortunately, it makes a big deal of space
and time difference when I use pointers to integers rather than simply
integers! In fact, my advisor would shoot me if I did the former. Space loss
is evident. But the worse case comes from losing "cache coherence", a fine
point that can change the speed 5 fold sometimes!!!!! Memory hierarchy is
like magic!
Thanks to Brian Hurt and David Gurr who wrote off-the list that bigarrays
would work for me. It looks like Bigarrays can do unboxed arrays of integers.
Cheers,
--
Eray Ozkural (exa) <erayo@cs.bilkent.edu.tr>
Comp. Sci. Dept., Bilkent University, Ankara KDE Project: http://www.kde.org
www: http://www.cs.bilkent.edu.tr/~erayo Malfunction: http://mp3.com/ariza
GPG public key fingerprint: 360C 852F 88B0 A745 F31B EA0F 7C07 AE16 874D 539C
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2003-04-28 18:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-27 21:34 Eray Ozkural
2003-04-28 16:40 ` Brian Hurt
2003-04-28 18:29 ` Eray Ozkural [this message]
2003-04-28 18:43 ` Brian Hurt
2003-04-28 18:51 ` Eray Ozkural
2003-04-28 19:05 ` Brian Hurt
2003-04-28 19:05 ` Eray Ozkural
2003-04-28 19:07 ` Falk Hueffner
2003-04-28 19:21 ` Karl Zilles
2003-04-29 10:52 ` Markus Mottl
2003-04-29 14:10 ` Hal Daume III
2003-04-29 15:46 ` Markus Mottl
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=200304282129.27582.exa@kablonet.com.tr \
--to=exa@kablonet.com.tr \
--cc=brian.hurt@qlogic.com \
--cc=caml-list@inria.fr \
--cc=erayo@cs.bilkent.edu.tr \
/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