Pages are timing out before they can load

Started by Stephen Clancy Reed on Thursday, October 15, 2015
Problem with this page?

Participants:

Showing all 7 posts
10/15/2015 at 4:44 AM

After the recent maintenance on the website, I have been running into profiles that are timing out before they can load.
This has gotten frustrating. For example; I get on a role, following a line in the family, and get to Joan of Acre, and the page will not load.
This is happing with many pages. I have put in a service request for this with Geni, but have not seen or herd anything else about it yet.
Anyone that can help fix this, I encourage you to.
Thanks
Stephen C. Reed

10/15/2015 at 4:57 AM

Mike Stangel I'm also timing out - better since the maintenance, but still there. Several times when loading documents. Makes it slow going.

10/15/2015 at 12:18 PM

We released some code changes to try to mitigate the effects of the timeouts that are occurring on profiles with many confirmed matches. Our logs indicate there are many fewer profile timeouts -- can you confirm?

10/15/2015 at 12:39 PM

Just tested with a previous time out / slow load profile. Not speedy, but no time out. Much better. I'll test with a document next.

10/15/2015 at 12:47 PM

Document (link from Internet) did very well, same profile with many matches.

Private User
10/15/2015 at 2:58 PM

Can we have an option not to show confirmed matches? I can't for the life of me work out how a confirmed match helps me, and it makes a mess of an otherwise good looking profiles presentation.

The reasons for confirming a match seem to vary, depending on who you talk to, so there's no specific difference between a confirmed match and an non-confirmed match. If you want one, just click the circle on the tree.

10/15/2015 at 3:43 PM

Private User, I have shared forcefully my profound hatred for this "confirm matches" feature in the past. It drains performance, impairs user experience, and provide virtually no value for genealogy research.

If there are users who like that features, then fine, let them knock themselves out with it.

But for the rest of us who wants nothing to do with it, I requested that we should have an option to turn it off. Back then, I have been agressively rebuked for making such a suggestion.

Maybe times have changed, and if there are enough of us--those who want to turn this feature off--perhaps we can get some traction this time.

You get my vote.

Showing all 7 posts

Create a free account or login to participate in this discussion