From: Michael <comtech.usa@gmail.com>
To: help-gsl@gnu.org, gsl-discuss@sources.redhat.com
Subject: seeking highly efficient caches scheme for demanding engineering computing?
Date: Fri, 27 Jul 2007 05:04:00 -0000 [thread overview]
Message-ID: <b1f16d9d0707262204h48dc972djedd99e44cc0f34e6@mail.gmail.com> (raw)
Asking for my friend...
seeking highly efficient caches scheme for demanding engineering computing?
HI all,
To same the time of costly function evaluation, I want to explore the
possibility of caching.
Suppose in millions of calls to the function evaluation, there are some
computations, in which only a portion of the parameters change, others
remain the same as the parameters that are used in some other function
evaluations some time before. To save time, I can group the varying
parameters into sub-groups, and cache the results for later use. This needs
a highly efficient cache and a efficient organzation and look-up. Also, the
decision of whether a group of parameters has been seen before should be
based on data trunk in binary form, instead of decimal formats, so I can
compare memory data trunks directly using memory comparison.
Does anybody have good suggestions and pointers on this approach?
Thanks!
reply other threads:[~2007-07-27 5:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=b1f16d9d0707262204h48dc972djedd99e44cc0f34e6@mail.gmail.com \
--to=comtech.usa@gmail.com \
--cc=gsl-discuss@sources.redhat.com \
--cc=help-gsl@gnu.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).