5000 profile limit?

Question

Just a question.   I've heard about a limit of 5000 profiles.  Is that mandatory or suggested.  At the moment I have just over 4000, which I've built up, one by one over the last year.  I'm proud to say, all but 1 are sourced.

I want to keep building up my extended family.  What happens when I hit 5000?  So far, I've had only a handful of merge requests and 3 trusted list requests, so managing them has not been any problem.

Answer 1

There's an answer by Chris Whitten in the reated question https://www.wikitree.com/g2g/114220/5000-profile-threshold (from 2014)

Seems mainly to be the risk of the bulk managment tool for the watchlist slowing down (or eventually locking up).

Like you I'm entering profiles manually - but since I have worried about this limit all along, I try to jettison people as I go, if they're not blood relations. So I'm only on 2700.

I rarely use the bulk removal tool - but a few times when I have requested trusted list access for the purpose of correcting a -son name that should be a -dotter name, I have gotten many more profiles than I asked for; then the bulk removal was useful.

Answer 2

It's not mandatory, but a bit more than "suggested" - it is strongly recommended.

You will find that the system responds slowly if you have a large watchlist and may even hang occasionally.

Answer 3

Before the 5000 limit was begun, I had racked up 13,800 souls on my watchlist.

Suddenly I was in non-conforming status. I kept getting warnings about the dire consequenses of my HUGE watchlist.

Since then, I have slowly whittled down my list, eliminating all but direct ancestors. I've cleaned it up from the first abut 1500, up to 1822, I'm down to just over 7800 and I've never  noticed any slow down in my browsing.

I try to orphan a few daily, after re-sourcing them, and adding anything I can find. I'm trying to leave them better off than they were, so to speak. I know in many instances I've found spouses, and children that I didn't have originally.

Its a recommendation, not a requirement.