Upgrade StorageEntering data makes Zotero unresponsive ID:164452951
Fore some time I have noted that the interface was unresponsive when adding or updating entries e.g. a new journal article.
Today I had to write a new child note. After writing a few characters (approx 7 to 25) the interface became unresponsive.
In Windows Task Manger i noted that the CPU allocation for Zotero raised from somewhere below 10% (often below 1%) to somewhere between 30% and 40%.
Tried to update different fields in the Info-section and add a new entry. Every time the CPU allocation raised to between 30% and 40% and the Status column in Windows Task Manager told that the program not was responding.
Tried to add a single dot in an empty abstract field. As soon as the cursor position changed to a different field in the Info-section the CPU allocation rose as reported above. When the CPU allocation was back to the usual level somewhere below 10% I deleted the single dot again from the abstract field and moved the cursor to another field. Again the CPU allocation rose.
My guess is that it could be an issue with accessing the database. Perhaps some sort of lacking index that result in a scan of a table.
Today I had to write a new child note. After writing a few characters (approx 7 to 25) the interface became unresponsive.
In Windows Task Manger i noted that the CPU allocation for Zotero raised from somewhere below 10% (often below 1%) to somewhere between 30% and 40%.
Tried to update different fields in the Info-section and add a new entry. Every time the CPU allocation raised to between 30% and 40% and the Status column in Windows Task Manager told that the program not was responding.
Tried to add a single dot in an empty abstract field. As soon as the cursor position changed to a different field in the Info-section the CPU allocation rose as reported above. When the CPU allocation was back to the usual level somewhere below 10% I deleted the single dot again from the abstract field and moved the cursor to another field. Again the CPU allocation rose.
My guess is that it could be an issue with accessing the database. Perhaps some sort of lacking index that result in a scan of a table.
The issue seems related to exporting the library with Better Bib Tex.
In
Edit > Preferences > Better Bib Tex > Automatic Export
I changed the "Automatic Export" drop down option from "On Change" to "Disabled".
Then I have to use the "Export now" button near the bottom of the option screen to update the BibTeX file that the Better Bib Tex plug-in exports from Zotero. (This trigger the high CPU allocation, however on a time decided by me).
There also seem to be an "When Idle" option for exporting the library. It perhaps had a bit better performance than the "On Change" option.
I have found a bit more explanation on the plug-in developer Emiliano Heyns' page https://retorque.re/zotero-better-bibtex/installation/preferences/automatic-export/. He seem to be aware of the performance issue for big libraries, so I have not reported the issue.
Unless there is an easy way to get the automatic export without the performance issue the manual export will be sufficient for me.
I am contented. Thank You! It will be fine to close this discussion.