You are on the right track. The big CPU hit is allocating the memory block and
locking it down for a write. Once the memory block
is locked down, the OS doesn't do any moving of it. Thus, your DMWrite()'s are quick.
I would suggest to allocate a block the
size of what you need for all of your writes and then just blast into the whole block.
The overhead to keep track of what you
wrote is more but the performance is increased.
Steve
Jason Garrett wrote:
> Does anyone have any ideas on how to improve the performance of the
> database as a workaround?
>
> We are able to create and DmWrite 4K blocks at a desirable speed, but
> creating and DmWrite-ing 20 byte blocks
> takes much longer (more calls to make).
>
> I'm considering creating a multi-record in one record database, and
> coding for that. While not impacting lookups,
> this would improve the writes hopefully based on what we've already
> seen.
>
> Has anyone walked this line already and have a strategy/idea/approach to
> take?
>
> On the side, I'm going to writing ~100,000 records. The WORD based
> index limits me to 64K records, right?
> So the best solution is to maintain a second database? Thats my
> intended approach. Any hints/suggestions on that one?
>
> TIA.
>
> Jason Garrett
> Wireless Data Services
> Ph: +64 9 3794710 Fax: +64 9 3797360
>
> --
> For information on using the Palm Developer Forums, or to unsubscribe, please see
>http://www.palm.com/devzone/mailinglists.html
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
