Replying to myself... > It looks like the DmCloseDatabase writes back the DB header, although I
That's probably not the right idea because closing the database happens always in exactly the same way, while the speed loss is apparent only in case when DBCache is full. It'll be rather that the T5 scans for free space in the DBCache and because it is full, it takes so long. Not a very good message for T5 users as every one sooner or later will fill up the DBCache. Isn't there any other way except a reset? The deeper I understand T5, the more I like T3. Jan Slodicka ----- Original Message ----- From: "Jan Slodicka" <[EMAIL PROTECTED]> To: "Palm Developer Forum" <[email protected]> Sent: Wednesday, March 02, 2005 2:57 PM Subject: NVFS performace - purging DbCache > Hello, > > there was enough discussion on NVFS so far, but (in my opinion) the > following behavior was not explained: > > First the summary: > After DBCache gets filled, the opening of the RAM databases dramatically > slows down. > > Actually the sequence of the operations that slows down is > DmOpenDBNoOverlay() with dmModeReadOnly > DmCloseDatabase() > (I eliminated all intermediate code for the test purposes so that it is sure > that exactly these commands are responsible for the effect.) > > It looks like the DmCloseDatabase writes back the DB header, although I > can't find any reason for it. > > Does anybody know a workaround? > > Best regards, > Jan Slodicka -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
