Since the NAND memory is sequentially accessed, I presume the write time is a function of (a) size of file and (b) number of records.
The good news on DmSyncDatabase() is that it is a single 68K function call to optimized ARM code.
But is there optimization built in to only write the parts of the file that have changed?
The whole discussion about padding in the NAND flash representation that's been going on here should answer this. Those files are organized so Palm OS can just write individual records back to NAND rather than having to rewrite the whole file. If a record's size changes enough, it might require rewriting the whole file (I think... I don't know if there's a chained record format there or not).
-- Ben Combee, Technical Lead, Developer Services, PalmSource, Inc. "Combee on Palm OS" weblog: http://palmos.combee.net/ Developer Fourm Archives: http://news.palmos.com/read/all_forums/
-- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
