Dallan, My account is barely working. Have I hit some maximum (trees x profiles ) that is causing or related to persistent stalls and 502 or 503 timeouts?
The performance of the Morrel-Klingsmith tree’s 51 profiles has slowed to a crawl for loading or updating data and frequently stall out entirely where other trees with fewer profiles are performing slowly but somewhat better. Most attempts to load data to ancestry profiles today simply stalled with a “wait” message that displays for hours.
I sometimes get gateway 502 or 503 errors as well just to complicate the question. The only other time this happens is trying to run a 7cm one to many tier 1 report. When I go to 8cm I usually squeak by so can I take this for ISP bottleneck? If so I will challenge comcast to live up to the upload rate I pay for.
I ran local cleanup programs and compared Edge with Chrome trying to load a 20k selection from a 40k plus m_ ancestry file. I have many more plugins in Chrome but concluded that there is little difference except that the Edge bug (still not showing the CM up and down carats in the filter box) still exists makes using Edge not possible for >20 K match files.
Your thoughts?? Server or db limits on profiles per tree-- where am I falling down? The only clue may be that a file with <18K matches did load in reasonable time. It seems to be the ones where the original data set exceeds 20k that bog down.