Thanks, Jeith.
Yeah, that was a typo - I was opening a resource and releasing it.
Now that I'm aware of such drastic differences between the debug and release ROMs,
I'll only profile under release.
Thanks for your help!
- Jeff
[EMAIL PROTECTED] wrote:
> I don't see DmReleaseRecord calling MemHandleSize. I see DmReleaseResource
> calling it. Is that the function you're calling?
>
> I DO see DmReleaseRecord calling MemPtrSize. But in both of these cases, the
> memory manager calls are being made only in debug ROMs. You might want to do
> your timing tests on release ROMs in order to get a more accurate profile.
>
> -- Keith
>
> DIAMOND JEFF <[EMAIL PROTECTED]> on 01/26/2001 12:38:57 PM
>
> Please respond to "Palm Developer Forum" <[EMAIL PROTECTED]>
>
> Sent by: DIAMOND JEFF <[EMAIL PROTECTED]>
>
> To: "Palm Developer Forum" <[EMAIL PROTECTED]>
> cc: (Keith Rollin/US/PALM)
> Subject: Re: Databse access performance...
>
> Well, the POSE profiler said DmReleaseRecord takes about 5,000 cycles and
> DmGetResourceIndex takes about 4,000 cycles. But that's 3
> times slower than I get from straight ticks timing - could all that slow down be
> due to running the POSE profiler? Or the way
> TimGetTicks works?
>
> It seems the slowest thing is DmReleaseRecord's calling MemHandleSize, which is
> really surprising, since I wouldn't have thought
> MemHandleSize would be so mammoth. Look how much you instantly learn about the
> PalmOS from a profile dump!
>
> Well, in any case, I appreciate all your help and the bottom line is that record
> access takes at least thousands of cycles vs none
> for feature memory or dynamic chunks.
>
> --
> For information on using the Palm Developer Forums, or to unsubscribe, please see
>http://www.palmos.com/dev/tech/support/forums/
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
