|
One thing to note: using composite columns as tag browser categories (the box "show in tags browser" is checked) is extremely cpu-intensive. It is even more expensive if the composite column is tags-like. Hiding the columns in either the library view or the tags browser does not change this.
Unfortunately, some time back I broke editing that check box in custom column setup, but didn't notice until today. Turning off that feature for an existing column should wait until the next calibre release (0.8.23).
Another thing that you can't do much about: using even one composite column as a tag browser category will cause all the composite columns for every book to be evaluated. The more complex your templates, the longer it will take. One thing you might try: general program mode templates ("program: ...") evaluate faster than the other modes because they are lexically analyzed once instead of on each use. If translating a template to GPM isn't too hard, then you might consider doing that.
|