I did't say that in my post, please read it again. If you have a deeper understanding of databases, schemas and especially those requirements behind Gedmatch to prepare the one-to-many list then you will understand how they are going to safe computing resources and even disk space with this move. Same btw for 23andme, both of them can exclude those anonymous from matching list that are usually prepared up front (and stored). The one-to-one is run on-the-fly, it means when requested by the user. BTW, everyone who ever has got a new cousin in a TG and needs to do all the one-to-one vs all other cousins knows how this work is increasing with every single new cousin. Tedious work. Apparently it's N to the power of 4 for every new customer though I haven't found out why (that's from a person who worked with Ancestry on their database requirements when they switched to a NoSQL solution). But it's surely N*N -1 Hope that makes it clearer computing power needed to run those queries for DNA genealogy are enormous, especially with such a large user base that they have. Andreas > On Nov 13, 2015, at 14:39, Brooks Family via <genealogy-dna@rootsweb.com> wrote: > > I don't see where it says they won't be able to do queries? > I don't see where it says they won't be able to generate a match list > from their kit, only that their kit won't appear on /other/ kits' match > lists: > "will no longer be shown in comparison results" > > further clarification is needed > >> On 11/12/15 11:33 PM, Andreas West wrote: >> I guess it all happens to ease their load on the server as this is their constant problem with so many users. >> >> As those without an email are excluded from queries there is less to computate. >> >> Andreas >> >>> On 13 Nov 2015, at 14:17, Brooks Family via <genealogy-dna@rootsweb.com> wrote: >>> >>> *Effective December 1, 2015, kits with hidden (private) email addresses >>> will no longer be shown in comparison results. If you have a hidden email >>> address, you can make it visible by clicking on the EDIT link at the bottom >>> of your DNA resources box. >>> >>> So will those who have hidden addresses still have access to our >>> data? It >>> sound like they will not be able to see the results but not sure if I am >>> reading this correctly >>> >>> OMG. The way I read this, it instantly makes private all email-less >>> kits. It doesn't state that a match list /for that kit /will not be >>> generated, just that it will not be on any other kits' match lists. >>> >>> I can see how the change would cut the amount of griping to gedmatch, >>> but IMO it doesn't solve the problem. Even if the kit owner decided to >>> give the kit an email, there's no requirement to answer an email or >>> share info. I have those now, anyway. >>> >>> Small matches aren't useful if a kit owner is unresponsive - but large >>> matches /are/ even when the owner is unresponsive! They can be used for >>> comparisons. And sometimes I can figure out who they are on the site >>> that the kit came from. >>> >>> Good grief. >>> >>> ------------------------------- >>> To unsubscribe from the list, please send an email to GENEALOGY-DNA-request@rootsweb.com with the word 'unsubscribe' without the quotes in the subject and the body of the message > > > ------------------------------- > To unsubscribe from the list, please send an email to GENEALOGY-DNA-request@rootsweb.com with the word 'unsubscribe' without the quotes in the subject and the body of the message

The N to the power of 4 is probably because they are checking phased haplotypes. They need to compare both of your haplotypes with both of the haplotypes in the other party. Ann Turner On Fri, Nov 13, 2015 at 4:32 AM, ahnen@awest.de via < genealogy-dna@rootsweb.com> wrote: > I did't say that in my post, please read it again. If you have a deeper > understanding of databases, schemas and especially those requirements > behind Gedmatch to prepare the one-to-many list then you will understand > how they are going to safe computing resources and even disk space with > this move. > > Same btw for 23andme, both of them can exclude those anonymous from > matching list that are usually prepared up front (and stored). The > one-to-one is run on-the-fly, it means when requested by the user. BTW, > everyone who ever has got a new cousin in a TG and needs to do all the > one-to-one vs all other cousins knows how this work is increasing with > every single new cousin. Tedious work. > > Apparently it's N to the power of 4 for every new customer though I > haven't found out why (that's from a person who worked with Ancestry on > their database requirements when they switched to a NoSQL solution). But > it's surely N*N -1 > > Hope that makes it clearer computing power needed to run those queries for > DNA genealogy are enormous, especially with such a large user base that > they have. > > Andreas >

Ann, you're brilliant! Didn't think about that, so true. Andreas (WEST) born BASSO My ancestors: [http://www.wikitree.com/genealogy/Basso-Family- Tree-23](http://www.wikitree.com/genealogy/Basso-Family-Tree-23) "Ann Turner via" <genealogy-dna@rootsweb.com> wrote: > The N to the power of 4 is probably because they are checking phased > haplotypes. They need to compare both of your haplotypes with both of the > haplotypes in the other party. > > Ann Turner