|
As far as I know searching is almost never a bottleneck, unless you have either
1) Very large amounts if text in some metadata (for instance I know some people who put the entire book text in the comments field)
2) Use custom columns built from other columns, this means that doing a search causes the column to be evaluated for every single book at once, instead of on demand as is normal.
Both these cases can be mitigated by reducing which columns a prefixless search searches in Preferences->Searching
As far as I know, on commodity hardware, calibre can handle libraries of about 50K to 100K books with reasonable performance. If you search these forums you will find many tips on improving performance for large libraries.
|