Log in
Sign up
View all  |  Close all
#
Subject
Posted by
Actions
1
Deleting large outdated tree copies & SmartMatch initiation for large trees
Paul J. Lareau
- Close

I am in the process of updating my MyHeritage Web Site in preparation for extending my subscription, and I need some help on two questions.

My Web Site (LAREAU WEB SITE) contains the following Trees: 

FAMILY - Earlier Version  (400,879 individuals)

FAMILY - 15 Sep 2011  (465,536 individuals) 

FAMILY - 18 Aug 2012  (479,764 individuals)  *Default Tree

HMAV Bounty - 1  (9,661 individuals)

HMAV Bounty Collaterals  (9,302 individuals)

First of all, I need help deleting 2 of these trees.   FAMILY - Earlier Version was the original tree on this site and is outdated by 7 years.    This tree had over 1,300,000 SmartMatches, about 500,000 of which were responded to awaiting the other member's response.   When I removed the SmartMatching from this tree a few weeks ago, those SmartMatches went away (as I intended, as many were matching to possibly obsolete entries).   FAMILY - 15 Sep 2011 is a revised and updated version of the Earlier tree, but is now outdated by 1 year and replaced by the most current version.   This tree was never connected to SmartMatching, as I only treated it as an interim update, and was still concentrating on the SmartMatches of the Earlier version.  

The most current version of this tree is FAMILY - 18 Aug 2012, which I put up by GEDCOM on that date.  I have designated that as the Default Tree, and have set it up for SmartMatching.   My question is how long I can expect it will take before SmartMatching begins, and if either its size and/or other ongoing system changes are occurring that is or could delay its start.   There does not seem to be any problem displaying the tree or searching on it, though it did take about 2 weeks after loading for that to be accomplished.

The other two small Satellite Trees (HMAV Bounty and HMAV Collaterals) are both processing SmartMatches and displaying with no problems, and for now, I have been concentrating on working with those until the main database starts working.

Thanks for your help.

Paul J. Lareau 

 

   

 

 

Paul J. Lareau
- Reply
2
RE: Deleting large outdated tree copies & SmartMatch initiation for large trees
Richard9874
- Close
I used to delete my old trees all the time after uploading  new updated trees via Family Tree Builder. The Smartmatching would take no longer than 2 days to update on the new tree.  This all changed about 3 months ago and the Smartmatching no longer functions. I regret deleting my old trees now with the stored Smartmatches. 
Richard9874
- Reply
3
RE: Deleting large outdated tree copies & SmartMatch initiation for large trees [2]
Rafael Perel
- Close

 

Hi Marco, 

 Please note that each time that you publish your tree to the site the Smart Match calculation process is restarted. This means that if you publish your tree very frequently you may experience a large delay in receiving the new Matches. 

I have now made a change in the database so that your site's Matches will be processed faster. Please wait 3 days without publishing a new version of your tree to the site, and you should receive Matches. 

If this does not resolve the problem, please let us know. 

 

Rafael Perel
Israel
- Reply
4
RE: Deleting large outdated tree copies & SmartMatch initiation for large trees [2]
Paul J. Lareau
- Close

Thanks for the information, Marco.   I have the feeling that they may be doing some major changes to SmartMatching, although it is still working on my two satellite trees (not related to my large tree).    I have always rather worried that having two outdated huge tree versions out there (and the resulting 1,300,000 persons on the Web Site, along with 1,300,000 SmartMatches that have supposedly been archived on one of the outdated trees have been contributory to keeping the system moving slowly.    Things have started moving faster with the SmartMatches archived, but like you, I really would like to get the SmartMatching started on the current version of the tree.    

Paul 

 

Paul J. Lareau
- Reply
 
Loading...
Loading...