Performance issues and thoughts on how to address them
I noticed that Zotero does a refresh of the article list every time a tag is deleted even if the the tag was not active at the time. If the deleted tag is not selected, it should not change the results in the article list and the refresh seems a bit unnecessary. With 1.5b2 these refreshes make it slow to clean tags from a large library.
This could be fixed by making the tag setter in collectionItemTree to check if the new tags actually differ from the previous tags and only do refresh if they do.
A fix is available here
http://rafb.net/p/fE5B8V79.html
Also, when I investigated this performance issue with profiler, I noted that a major bottle neck in refreshing a large collection is sorting the collection with javascript's Array.sort(). If this sorting could be done in SQLite instead, the performance might improve.
Mikko
This could be fixed by making the tag setter in collectionItemTree to check if the new tags actually differ from the previous tags and only do refresh if they do.
A fix is available here
http://rafb.net/p/fE5B8V79.html
Also, when I investigated this performance issue with profiler, I noted that a major bottle neck in refreshing a large collection is sorting the collection with javascript's Array.sort(). If this sorting could be done in SQLite instead, the performance might improve.
Mikko
This is an old discussion that has not been active in a long time. Instead of commenting here, you should start a new discussion. If you think the content of this discussion is still relevant, you can link to it from your new discussion.