Quote:
Originally Posted by chodsdon
Shouldn't the first page load fairly quickly..while the db continues to organize in the backround?
|
No. Calibre first searches to apply any format limits and restrictions, then sorts the output, then picks the first N to display. Unless you are applying a restriction, it is probably the sort that is taking the time.
Quote:
|
Big searches cause the same error message. ie.."a" and "ab" while "abc" comes right up..so it does seem size dependant.
|
Consistent with the above. First calibre searches, then sorts the results.
You might try to do a 'check database integrity' (preferences -> advanced). It has the side-effect of reorganizing the DB and regenerating all the indices.
You can test the timeout hypothesis relatively easily, if you are willing to hack a little bit. The idea is to copy the content server client-side files (javascript, etc) from the install directory to a local one, change the timeout (in gui.js), and try it.
Steps:
1) Open a file explorer on your calibre configuration directory. Preferences -> Advanced -> Open Configuration Folder will take you there.
2) Create a folder named 'resources'. Navigate into that folder.
3) Open another file explorer on your calibre install folder. Open the 'resources' folder.
4) Copy (not move!) the folder content_server from the explorer in step 3 (the install folder) to the explorer in step 2 (the resources subfolder of your configuration folder). You can delete all the files in the new content_server folder except the one you will change in the next step: gui.js.
5) In the resources/content_server folder in your configuration folder, edit the file gui.js. If you are on windows, don't use notepad but instead use wordpad or a programmer's editor, so that line endings will be correct. Change the number on the line
var LIBRARY_FETCH_TIMEOUT = 10000; // milliseconds
to something larger, perhaps 20000.
6) see what happens.
Be sure to delete all the copied folders once (if) an 'official' fix is provided.