When loading SM's in response to an email from a large database, and the number of SM's exceeds about 2,000, it can cause a Server Timeout. Timeouts also totally disable the "display candidate SM's by name" function on my own very large database. While this is an inconvenience, I understand that it might be unavoidable due to scaling (my db = 400,000 people, and has amassed 1,200,000 SM's), and it can be lived with.
But a possible solution might be to use something like the segmenting function you use in the family trees, and display only the next 500 and provide a "next 500" button rather than a timeout. That way the user can begin to whittle down overly large SM lists rather than just ignoring them.
No reply necessary. Just a thought that might help those with very large databases get SM's under better control.