[Kde-pim] Akonadi db schema change needed to store search folder queryStrings

[Will Stephenson]

On Thursday 23 Feb 2012 22:26:49 Shaheed Haque wrote:
> Is the extra storage really a concern? I suppose the pimitemtable is
> probably going to have most entries by far. That seems to have a
> handful of columns which might be strings (and 9 in total). Even if I
> had a million records, we are talking a handful of MB.
> 
> That seems perfectly reasonable...Or have I misunderstood?

Multiplying the number of rows by the number of QString columns and summing it 
across all tables gives me (2 imap accounts, about 2.5GB mail in total on the 
servers) an additional 1455755 bytes for the storage. Then I assume indexed 
columns count double, which gives another 872906 * 2 bytes as there are 2 
indices on parttable.name (which contains a lot of repeated entries, perhaps 
it would make sense to normalize this out into its own table?).

That's 3201567 extra bytes in theory.  I'm not a database guy so don't know 
how that translates into real extra storage, memory footprint (indexes stay in 
memory, right?) and performance.  Can someone better informed comment?

Will

_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/