Script issue causing Zotero slowness and irregularities

BaiYian
Hello,
Some people noted that Zotero is slow to start or proceed with some tasks. I have an issue in that department and sincerely hope I can get some help to sort it out.

PC SPECS
OS: Windows Vista Home Edition Premium
Processor: Intel Core2Duo T9300 2.5GHz
Memory: 3 GB | VideoCard: GeForce 9500M GS

BROWSER Info
Firefox: 3.0.11
ADD-ONS
Cooliris 1.10.1 - ForecastFox 0.9.10.1 - Microsoft NET Framework Assistant 1.0
Zotero 1.0.10

ITEMS in library: 4940


ISSUES
1) Zotero is really slow when you start it.
Read the threads about it but I wanted to underline it. It does take more than 3 to 5 seconds to cache data before launching make it more in the area of 30 seconds and up.
2) When adding a new items with the Create-New-Items button, I got this message:
A script on this page might be busy or doesn't work anymore. You can stop this script now or wait and see if the script will resume.
Script: chrome://zotero/content/xpcom/db.js.164
After clicking the continue button, the action completes a little after.
3) When taking a snapshot of a web page, I also got this similar message:
A script on this page might be busy or doesn't work anymore. You can stop this script now or wait and see if the script will resume.
Script: chrome://zotero/content/xpcom/db.js.168
After clicking the continue button, the action completes a little after.

I did check the database integrity and all came back normal. No issues there.

I tried the latest beta version of Firefox (V.3.5 beta 4/99) to see if it could solve my issue. Here's my observations:
1) Zotero launch is painfully slow, slower than with the V.3.0.11. A solid minute and up.
2) Script: chrome://zotero/content/xpcom/db.js.164 & 168 messages don't come up when I create a new item or take a snapshot. However, it takes Zotero forever to accomplish these two tasks and I mean forever. A solid minute and up.

Problems with either Firefox versions really hinder my use of Zotero. Not throwing the towel because it can be worked out and Zotero fits my need. I must say though that I did not try it with the latest Zotero version (2.0b5). When I tried to update, the process seemed to stall and take forever. Might be the number of items of my library that makes the process so slow.

One last comment, I did not use the Zotero Database Repair Tool because my SQL file (120MB) is above the limit specified.

I'll be glad to read your comments and suggestions.

Best,
CEP
  • dstillman
    my SQL file (120MB) is above the limit specified.
    That's likely to be your problem. 120MB is fairly massive for a Zotero database and is likely the result of a very large full-text index (e.g., from lots of large snapshots and PDFs). How many indexed words does it say there are in the Search pane of the Zotero prefs?

    We'll be switching to a more efficient full-text indexing system in an upcoming release, which should help. In the meantime, you might consider clearing your full-text index (and perhaps setting the options to 0 to temporarily disable further indexing) to speed things up.
  • BaiYian
    Correction 121MB. I usually take a snapshot of the web page for each bookmark and I often take a snapshot of web page where info are related to that note/bookmark. I prefer to have a idea of how and what was on that weblink than just the link to that page. Lots of snapshots but no PDFs though (yet).

    What about the notes
    Script: chrome://zotero/content/xpcom/db.js.164
    Script: chrome://zotero/content/xpcom/db.js.168
    What does it mean?

    Dan Stillman:
    "How many indexed words does it say there are in the Search pane of the Zotero prefs?"
    ME:
    Indexed >>> 6916
    Words >>> 173 602

    Dan Stillman: "We'll be switching to a more efficient full-text indexing system in an upcoming release, which should help."
    ME: What (kind) improvement is expected with this change for the user?

    Dan Stillman: "In the meantime, you might consider clearing your full-text index (and perhaps setting the options to 0 to temporarily disable further indexing) to speed things up."
    ME:
    1) Dan, clearing my full-text index and putting indexing value to 0, what impact this will have on the data I already captured with Zotero? Will I loose data I would not want to? This repository is really important to me. I have to make sure.
    2) Does this will clear the problem I had when creating a new item or taking a snapshot?

    Thank you for your time and quick response, Dan! Much appreciated!

    Cheers
  • noksagt
    1) Dan, clearing my full-text index and putting indexing value to 0, what impact this will have on the data I already captured with Zotero? Will I loose data I would not want to? This repository is really important to me. I have to make sure.
    You could make a copy (backups are a good idea anyway) before hand, but it will only remove the ability to search the full text of your snapshots from within Zotero. All snapshots and references will remain. You could re-index your current snapshots at some later date if you miss the full-text search.
    2) Does this will clear the problem I had when creating a new item or taking a snapshot?
    Probably: it should shrink your database & you will no longer have to wait for new snapshots to be indexed.
  • BaiYian
    Thanks to both of you for your input.
    I always backup data. As suggested I cleared my Full-text Index & I set it to O. zotero.sqlite is now at 9MB. I noticed Zotero was speedier but I still receive script malfunction notes while:
    - adding snapshots
    - adding new items.
    These error notes makes it impossible to add a lot of items quickly.
    BTW, previously, I reinstalled Firefox & Zotero from fresh to see if that wasn't the problem. I still get those error notes.

    After clearing the Full-Text Index, I tried to add items and snapshots. Here's what I receive from Zotero:
    Warning/Error note
    Script : chrome://zotero/content/xpcom/db.js:913 (6 times)
    Script : chrome://zotero/content/xpcom/data_access.js:3591 (4 times)
    Script : chrome://zotero/content/xpcom/zotero.js:1181 (4 times)
    Script : chrome://zotero/content/xpcom/db.js:773 (3 times)
    Script : chrome://zotero/content/xpcom/db.js:164 (3 times)
    Script : chrome://zotero/content/xpcom/db.js:168
    Script : chrome://zotero/content/xpcom/zotero.js:462
    Script : chrome://zotero/content/xpcom/db.js:263
    Do you think this still is my problem or is it related to a Zotero malfunction?

    I used the database repair tool once my database folder became smaller but, after, I keep getting the above notes.

    Have any idea where to look at to solve this?
  • dstillman
    Go to about:config in the Firefox address bar, look for dom.max_chrome_script_run_time, and set the value to, say, 60 (seconds).
  • BaiYian
    Dan,
    I made the change you suggested to dom.max_chrome_script_run_time. Since then I do not receive any notice. Better but I keep thinking what is the source of my issue.
    - Is this issue related specifically to Firefox or Zotero inner workings?
    - Will newer version of Firefox and/or Zotero solve that issue?

    On another note, I tested how much time it takes to Zotero to add a new item and to add a snapshot.
    New item: 79 sec.
    Snapshot: 43 sec.

    These numbers seem high to me and the feel of it look slower than before to me. I still have to add close to 7000 new items to my Zotero.
    What is your take about my situation? Is my Zotero is slow or is this normal input time?
    Does the Zotero Team waiting for Firefox new features/implementation to add to Zotero firepower?

    Thank you for your help!
  • adamsmith
    doesn't the time for snapshot and new item depend on the connection and what Zotero has to download?
  • BaiYian
    Valid question, adamsmith!
    I use a cable connection (Videotron, Montreal, QC) which is stable. I regulary have the same speed (Download/Upload) as the below results:
    Download: 7.21 Mb/s
    Upload: 0.79 Mb/s
    Speed Test link: http://www.speedtest.net/result/497187689.png

    This combine to my PC specs leads clearly the issue is neither the internet connection or the PC used.

    I tested several times the duration it takes Zotero to create a new item, and a snapshot.
    TEST 1 TEST 2 TEST 3 TEST 4
    Item: 76 sec. Item: 82 sec. Item: 85 sec. Item: 84 sec.
    Snapshot: 42 sec. Snapshot: 43 sec. Snapshot: 42 sec. Snapshot: 43 sec.
    TEST 5 TEST 6 TEST 7
    Item: 85 sec. Item: 85 sec. Item: 84 sec.
    Snapshot: 43 sec. Snapshot: 44 sec. Snapshot: 44 sec.

    As you can see, I consistently log the same kind of duration for new item creation and taking snapshots. Like I mention previously, these numbers are far more longer than what Zotero used to give me.

    Does Zotero has known issues about this?
  • dstillman
    Try closing the tag selector (using the icon to the left of the gear icon) before saving, or saving into an empty collection.

    Note that you're using 1.0.10, which likely won't be receiving any more updates. If you're concerned with speed, upgrade to 2.0b5, which should be faster in many ways. The upgrade may take a little while with a large library, but just let it go when you'll be away from your computer.

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.