From: "Michał C" <ciebiada@gmail.com>
To: caml-list@yquem.inria.fr
Subject: Question about optimization
Date: Sun, 2 Nov 2008 03:52:49 +0100 [thread overview]
Message-ID: <BDD33495-2267-4A95-8C60-ACB2979E450D@gmail.com> (raw)
Hi!
I'm working on a physical based ray(path) tracer and the performance
is one of my top priorities (just after the image quality).
So I have a question about optimization: can You share some tips or
maybe optimizing strategies to improve the speed of programs?
here is my code: http://neos1.ovh.org/ray3.ml,
and here is how I compile it:
ocamlopt -inline 100 -unsafe -ffast-math str.cmxa -I +lablgl
lablgl.cmxa lablglut.cmxa -o ray ray.ml
Maybe You can take a look, sure I don't expect You to look through it
in some hardcore way, but You know, maybe there are some obvious
mistakes or unnecessary boxing which will spot your eye.
Thanks in advance,
oh and if you possibly want to see the development or how the program
works - http://neos1.wordpress.com
Regards
next reply other threads:[~2008-11-02 2:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-02 2:52 Michał C [this message]
2008-11-02 12:23 ` [Caml-list] " Peng Zang
2008-11-02 13:02 ` Jon Harrop
2008-11-02 15:52 ` Jon Harrop
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=BDD33495-2267-4A95-8C60-ACB2979E450D@gmail.com \
--to=ciebiada@gmail.com \
--cc=caml-list@yquem.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