Fixing slow performance by partitioning of database
Dear all,
With more than 6.000 items in my database, Zotero has become somewhat slow. Especially when I type a word in the search box, the browser is blocked for some while.
Has anyone good ideas how splitting the zotero-database can be done in an intelligent way to get rid of that problem?
I put the bigger part of my notes in my "old zotero" (which I took off from sync) and started to work in a collection containing only the last six months. I plan to import that new collection into the old one regularly.
But now I have to work on an old topic.. .and I start to switch between the two databases. Which means re-starting Firefox all the time.
With an ever-growing database - and the future technical development of Zotero in mind - what could be a good solution for this?
With more than 6.000 items in my database, Zotero has become somewhat slow. Especially when I type a word in the search box, the browser is blocked for some while.
Has anyone good ideas how splitting the zotero-database can be done in an intelligent way to get rid of that problem?
I put the bigger part of my notes in my "old zotero" (which I took off from sync) and started to work in a collection containing only the last six months. I plan to import that new collection into the old one regularly.
But now I have to work on an old topic.. .and I start to switch between the two databases. Which means re-starting Firefox all the time.
With an ever-growing database - and the future technical development of Zotero in mind - what could be a good solution for this?
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.
Many of us have pointed out that the search bar is virtually useless as it is right now -
http://forums.zotero.org/discussion/10306/quick-search-not-so-quick-let-us-optionally-search-just-title-author-and-not-fulltext/
I'd recommend either just not using it or turning off full-text indexing.