Recently I updated my desktop to RM 11.1.0 and all was fine until I started using Webhints on Ancestry with a 22MB file. Although the feature still works, it is extremely slow in matching data. I’ve tried several people in one file and I also used people in another RM 11 file and got the same result. Major delay. The Webhints interface just displays a spinning freeze. I’ve tried several corrective measures like indexing, open/close file, etc. Still have delays. See image below. So, I then opened the same file on my laptop running RM 11.0.4 and did not experience any delays in displaying the Webhints data. Win11 32G Memory, SSD, RM 11.1.0, No VPN, good internet service.
Is anyone else experiencing this delay on Ancestry.com webhints?
Tried my database and it was slow BUT only took abt 30 seconds to load-- that said this particular file has very few web hints–so if you have a lot it might take quite a while
In my case, it took 30-65 seconds to display data for each person in RM 11.1.0. Using RM 11.0.4 it took less than 5 seconds. If patient, it does work to display the data but it’s much slower than before.
We noticed the speed fluctuating while testing the new Ancestry API. We probably have a lot of users uploading and downloading today. I’m sure things will settle down once Ancestry is no longer supporting two APIs at the same time.
I tried downloading my Ancestry tree over 25K+ people it took less than 10 mins since its a now a NEW database – will have to wait till some thing has changed on ancestry side and/or test changing on RM side
Yes. That was my experience last evening as well. In addition, it seems hints are not displayed correctly/updated in RM i.e. RM showed no hints but Ancestry showed several hints on their system.
“I tried downloading my Ancestry tree over 25K+ people it took less than 10 mins”
I would think that the Ancestry download feature would have code that would respond much quicker than the Webhints API. Could it be that Ancestry may be fully running both the new and old Webhint APIs and then connects the API output to the appropriate format? I don’t know but the API(s) behavior seems to be independent of data volume. In other words, the delay is almost the same regardless of the person’s record size. I’ll try another test tomorrow about 5am EDT.
In my experience Treeshare has working well so far with the update. I am able to update the tree in either direction. Ancestry Webhints, however, seems to be so much slower.
This morning at 5am EDT I again attempted to use Ancestry Webhints on RM 11.1.0 and experienced almost the same delay in getting the return screen, about 30-60 seconds per person. So I don’t think the issue appear to be related to system load. It could be running two API’s at this time. I don’t know what the issue is but the current response time on the new API is not responsive enough to use Ancestry Webhints. So I’ll return to using 11.0.4 while the issue is being worked. Thanks for your help.
just note that you like have probably less than a month before you have no option.
I tested with my tree and so far the response had been nearly instant – but I downloaded from Ancestry — I did not have a RM11 tree to test that was connected to ancestry…
Just upgraded. When I launched TreeShare on my main tree it took 10 or 15 minutes to load the dialogue (enough time to make a pot of coffee and have a chat!) and just then displayed the 5 people I know should have been on there - not my whole tree (phew). Closed down RM, rebooted and TreeShared (if that’s a word) again. Only took a few seconds and worked perfectly. I suppose being in the UK might help a bit with speed if there is a smaller user base.
To clarify–I’ve not had any issues with Ancestry Treeshare. It works fine for me in RM 11.1.0 to make RM file and online changes. The issue is with the delayed response time of Ancestry Webhints using RM 11.1.0.
I have tried TreeShare twice since the 11.1.0.0 upgrade. This is just to run TreeShare and see what’s different, not to do an upload or a download. It’s also not looking at Ancestry Web hints.
Yesterday, it ran extremely slowly, got stuck at 99%, and never finished.
Today, it ran much faster (but still slower than it used to run), and completed just fine without getting stuck.
This is on a brand new and super fast Windows 11 computer with eight i9 processor cores and 32GB memory. My Internet was running at about 300Mb each time. So the time TreeShare was extremely slow and got stuck, the problem had to be on the Ancestry end of the connection.
I’m also seeing the Ancestry WebHints screen being very slow. I saw it faster during testing so I know its capable of faster speeds than what we are experiencing now.
my thoughts were it was less likely to be a RM issue - but people like pointing fingers sometimes.
Still curious what was the root cause or if just mostly load/demand issue
RootsMagic has no control over the speed at which webhints travel back and forth via the API. Ancestry is the postman and your ISP is the mail truck. Apologies to you, Jerry, for mistakenly linking you to my reply.
