With MemHandleLock, once it's locked, if you lock it again it doesn't take too much time, it basically just increments the lock count. Therefore, you do not have to make dramatic change to your code, just lock it once before you call a stack of functions, and unlock it when it's done. LionScribe
"Flex" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Concentrate your efforts on MemHandleLock - it's hell slow operation. If > you can avoid some of the locks (by pre-locking for example) you'll be > happy. > Also if you can share one single buffer for all your... hm... records? I > mean allocate the maximum length and save a couple of new/lock/unlock/free. > > kshaff03 wrote: > > My app is a little slower than I want it to be. There are some things that I > > think I can do a little better to speed it up. I was wondering what common > > operations on the palm take the most amount of time. These are some of the > > operations that I am using in my function, but feel free to mention others. > > > > > > MemHandleNew/Lock/Unlock/Free > > > > StrAToI(...) > > > > if (char[index] != NULL) //I assume this usually takes only one > > comparison > > > > setText(Field, string) > > > > > > > > > > Also, is the function "TimGetTicks()" an effective way to measure > > performance > > of a single or small number of operations, or is this an imprecise > > measurement? > > > > Thanks > > > > Kevin > > > > > > > -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
