From: "Adam P. Jenkins" <ajenkins@netway.com>
To: Michael Hicks <mwh@dsl.cis.upenn.edu>
Cc: caml-list@inria.fr
Subject: one-time initialization
Date: Thu, 28 Jan 1999 08:03:56 -0500 [thread overview]
Message-ID: <199901281303.IAA00542@xcom-78-133.mdc.net> (raw)
In-Reply-To: <199901280508.AAA21644@codex.cis.upenn.edu>
Michael Hicks writes:
> I wonder if anyone knows how to optimize the following (simplified for the
> sake of dicussion) situation:
>
> let global = ref None
> let init i =
> global := Some i
> let f () =
> match (!global) with
> Some x -> x
> | None -> failwith "not initialized";;
> let g() =
> match (!global) with
> ...
>
> Essentially, there is some global state that is initialized once, and is
> used by all functions in the module. In a more realistic situation, this
> state might be initialized by reading in a file. Given that following
> initialization the global state never changes, it should be conceivable to
> eliminate the match and dereference; on my machine (pentium 166), the match
> and dereference result in about a 30% slowdown. I've fooled around with
> some things, but haven't found anything that performs better than this
> straightforward approach or is any more elegant.
If you're reading the state from a file, then you could make global
not be a ref by writing
let global = readState "initFile"
You could even store the init filename in an environment variable so
that readState could read a different file on different program
invocations.
As far as getting rid of the pattern matching, if the state can only
be one of several choices, then you could make several versions of f()
and g(), one for each pattern, and assign them from readState. That
is.
let (global, f, g) = readState "initFile"
where readState returns different functions for f() and g() depending
on what state it reads.
Adam
next prev parent reply other threads:[~1999-01-28 19:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-28 5:08 Michael Hicks
1999-01-28 9:54 ` John Prevost
1999-01-28 14:47 ` Michael Hicks
1999-01-28 10:38 ` Xavier Leroy
1999-01-28 13:03 ` Adam P. Jenkins [this message]
1999-01-28 20:23 ` Gerd Stolpmann
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=199901281303.IAA00542@xcom-78-133.mdc.net \
--to=ajenkins@netway.com \
--cc=caml-list@inria.fr \
--cc=mwh@dsl.cis.upenn.edu \
/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