Need Quick Logon To Ancestry

RootsMagic
21

Go to Settings, WebHints and click on Reset TreeShare and see if that helps.

22

Doesn’t a reset do a disconnect? I could be wrong about the disconnect, but I certainly don’t want a disconnect to happen by accident.

Even so, I actually do a disconnect and reload my ancestry tree periodically. Wouldn’t that do a reset?

23

Reset is not supposed to disconnect.

Disconnect and Reloading should result in more or less the same state as Reset but maybe not. One thing you might check is whether the AncestryLinkTable is emptied by Disconnect. I think it should be.

1 Like
24

I only did this test in RM9 on the theory that it’s really only RM9 that matters in the long run.

After the reset, the time on RM9 went from 1:55 to 6:47. I shut RM9 down, started RM9 back up, and signed on to TreeShare again. This time it went back down to about 1:50. There is always some variability in the timing.

I gather that the time went up so much after the reset because it had to rebuild a table or a file that had been deleted by the reset. However, the entire 6:47 was completely CPU bound with I/O only running at about 0,1 MB/sec.

25

from my limited experience—a disconnect is used when you want to break the link to a specific tree-- such as the other day, I downloaded one tree from Ancestry and then wanted to download a different tree-- so I had to use the disconnect

26

The DT8 files are definitely used for data interchange, as I fixed my transfer problem by copying the DT8 file from a working machine to a non-working one. The journal file is created during login and data interchange, because I watched the directory while it was happening. The DT8 file has several tables for citations, etc, and their associated guids and timestamps.

27

Will that not cause you to click until your hand cramps up?

28

Data interchange is internet protocols, incoming packets and data structures being constructed/formatted by program code. Subsequent program code would initiate SQLite-specific transactions accompanied by creation of the rollback journal. The one you replaced/overwrote with a fully-complete rollback journal may have been unfinished, truncated or corrupted. No telling. But completion of all SQLite transactions successfully then triggers program code to structure/packetize the desired return results for the API .