>At 23:29:14 7 Dec 1999 -0800, Scott Gruby
><[EMAIL PROTECTED]> wrote:
>
>I'm working on an application that uses a large static database
>which is broken down into 6 records each about 60K in size. ...
>then I tried doing the MemHandleLock at app startup on the 6
>records and keeping the pointers around (and then doing a
>MemHandleUnlock on app stop) and saw an even bigger speed increase.
>
>So my question is...is there a major problem with locking the
>handle at app startup and then unlocking it at app stop? Since
>I'm doing the locking early in the app's life, I don't think
>that memory fragmentation is a problem here.
I'm betting a lot on a successful outcome to this approach: I'm
doing the same with a database of roughly the same size, and
writing a whole ream of database code that expects to be able to
access records at fixed (for the duration of application
execution) memory addresses.
--Greg Lutz
