Jeff,
POSE provides a REALLY good way to answer your question.
Just prototype the 2 different variants and run a Profile session on each.
Details (down to clock cycles) are captured about both application AND Palm
OS code time used.
We have used profiling to optimize implementations with good results.
Then we viewed the profiling results on a MAC.
POSE profiling gave us insights into better combinations of Palm OS APIs to
use that are
difficult to get using any other approaches I am aware of.
This has allowed our applications to run pretty well on Palm OS 2.0 and up.
Reading about POSE profiling/searching the POSE forum should help...
I can't give you any info about Features performance as our apps do not use
them.
Regards,
Randy Maxwell
-----Original Message-----
From: DIAMOND JEFF [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 26, 2001 10:07 AM
To: Palm Developer Forum
Subject: Databse access performance...
I didn't get replies to my previous question on this subject.
I'm trying to decide in designing a project whether to use feature
memory or a database for a commonly accessed buffer.
I'd like to know what kind of things the PalmOS actually does internally
when you do GetRecord / MemHandleLock / MemHandleUnlock / Release Record
to get a sense of just how slow the process really is.
I'm specifically wondering if there is any "searching" done in the
process, or any vector traps / processor state changes, etc, which would
be much slower than a few ifs, branches, and dereferences.
True, I could just apply to receive the actual PalmOS source code, but I
don't really need that level of detail. :)
Thanks for the insight!
- Jeff
--
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/
