View Single Post
Old 06-22-2011, 10:19 AM   #11
yuri_b
Connoisseur
yuri_b will become famous soon enoughyuri_b will become famous soon enoughyuri_b will become famous soon enoughyuri_b will become famous soon enoughyuri_b will become famous soon enoughyuri_b will become famous soon enough
 
Posts: 71
Karma: 592
Join Date: Aug 2010
Device: irex dr800sg DR1000S
Thanks Gertjan

So indexing and limiting file viewing to fetch data for 3-4 pages will help.
And of course faster card will do magic

For now I will not consider indexing of all files, because I can do this once at night, but browsing books, if every page opens 2-5 minutes, drives me crazy

1) As new data base not created but merely copied from template we can just replace 1 template file and delete old global.db, or tell to every user how manually add indexes to db . Indexes are maintained automatically by dbase, every insert/update will update indexes. You don't need worry about this. AFAIK default index will speed browsing filename+directory without tag (no book, news or picture);

2) Fetching only few pages will require change in file viewer (ctb). Not difficult and not big change. Only one design problem I see in working with quick jump table: filling jumping. How to fill it optimally, without read all data, and how to calculate page where to jump without reading all data.

Sincerely
Yura

P.S. I didn't vacuum database, but I didn't remove any book, only add, so this is a real size.

Last edited by yuri_b; 06-22-2011 at 10:26 AM.
yuri_b is offline   Reply With Quote