Hi
T5 uses 512 By allocation units, early T650 as well, T650 Sprint update went
down to 36 By. E2 might use also 36 By. (Based on my fast check on the E2
emulator.)
Every DB record takes 1 or more allocation units.
So if your average record size is 50 By, then the DB size will grow 10 times
on T5.
Best regards,
Jan Slodicka
----- Original Message -----
From: "Jim Billmeyer" <[EMAIL PROTECTED]>
Newsgroups: palm-dev-forum
To: "Palm Developer Forum" <[email protected]>
Sent: Tuesday, May 03, 2005 12:43 PM
Subject: Re: T5 database HotSync file size problem
> Mikhail Barashkov wrote:
> >
> >> I am building pdb files externally and am HotSyncing them onto the T5.
> >> In doing so the pdb file size grows over 10x. The same pdb files
> >> HotSync onto a T3 and older PDAs have no appreciable change in file
> >> size. Yet even with the pdb file growth the palm applications can
> >> still read the files without any sign of corruption, but the
> >> application does run significantly slower then when the same
> >> application and databases are run on a T3.
> >>
> >> Any ideas?
> >
> >
> > Due to T5 memory organization, you lose an average of 256*n bytes on a
> > database, where n is number of records.
> > So the only solution is to decease num. of records in database.
> > Mikhail Barashkov
> >
>
> Thanks Mikhail,
>
> In my case the loss is linear as you suggested, but it is about 494
> bytes per record. Can it be really that bad? Is there anything other
> then reducing the number of records that can be done?
>
> Jim B
>
> --
> For information on using the Palm Developer Forums, or to unsubscribe,
please see http://www.palmos.com/dev/support/forums/
--
For information on using the Palm Developer Forums, or to unsubscribe, please
see http://www.palmos.com/dev/support/forums/
