At 4:41 PM +0200 21-04-00, William F. Weiher III wrote:
>I believe that the database header is 'smarter' and will actually use
>multiple chinks, but once you reach this point thinks 'really' slow down.
>You can certainly have more than 10K records (I have done it)
You're right! My error! (And I should know better.)
Turns out I was looking at the wrong function. Of course the database
header will expand to multiple chunks if it can't grow the unique one.
In practice, this almost never happens. Especially with big memory
devices, it's almost always possible to resize a chunk up to the 64K limit.
So only DBs with >8100 records (or DB's on very nearly full devices) will
have multiple database header chunks.
So this case might be exposing a performance problem with DB headers that
have multiple chunks.
The code to insert an entry into the middle of the list could be a lot
better. Would you happen to be using a conduit that tries to do that?
Normally new records are just appended to the end, and that should perform
fairly well, even if there are multiple DB header chunks.
I'd love to see a 'hd 1' of an empty device after installing just this DB.
I think that would help a lot to figure out if there's a bug or
optimization opportunity here. You can simulate that pretty easily with
Poser: just boot up a clean ROM and then drag the .pdb file onto the
screen. Then connect the debugger, open the console, type 'hd 1', wait a
really long time, and finally copy/paste the result into an email and send
it to me. :-)
--Bob
________________________________________________________________________
Bob Ebert, Consulting Engineer, Palm Computing Europe V: +33 4 9952.4354
77 rue Samuel Morse, 34935 Montpellier Cedex 9 France F: +33 4 9952.4397
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
