I will skip over why I am starting from scratch today but I deleted DEVONThink to Go (v3) from my iPad and installed it again, set up the config necessary to reach my WebDAV sync store.
One of my databases has 4000 items in it and the “downloading” step took 10-15 mins (sync is set to download on demand) but the “synchronizing items” step is at over an hour and counting.
Is there a way to see if there is something not working correctly? What is DevonThink To Go doing during this step? Since I’m starting with an empty DB on the iPad, what is synchronizing?
How large ((bytes) is this database actually? Is there enough space available on the iPad?
In Database properties the DB is ~12GB and ~5200 items.
The iPad storage space panel in Settings reports the DevonThink is using ~450 MB in Documents & Data.
The iPad had over 100GB of free space.
That should be no problem. It might become slow but usually only when you import like 50,000 to 100,000 items and with many tags. Have you started completely from scratch (means: you deinstalled both DEVONthink To Go 2 and 3 to clean the slate) or did you delete databases to start over?
This was after starting from scratch – meaning I deleted both Devonthink aps and downloaded just V3 and started there.
I have virtually no tags.
Ultimately, that second step “Synchronizing items” step took ~ 4hours to complete.
In this second step, is there anything still downloading or is the work all local to the iPad?
No, that is happening only local. As you are using a WebDAV sync store: Would I go too far if I asked if we could connect to the sync store and try it from here so we can experience it ourselves with the debugger attached? We’re by no means interested in the contents of the databases. If yes, please let us continue the conversation in PM or email.
Thanks for all of the quick back and forth here.
I’d certainly be open to following up in PM, and yes I am using a WebDAV store and it is one that I run on my own in my home network and make available externally but I am curious, since the step 2 (“synchronizing items…”) is all local, how does the WebDav server fit in?
Just trying to understand the “landscape” so I know we are on the same page.
Download the data does not seem to be the problem. The problem is applying the new data to the local database. And whatever it is in your data store that makes this so slow we’d like to see it in action so we can stop it in the debugger. If it runs smoothly here, we’ll need to think more about why it could be so slow for you and be fast here.