-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is it time to reconsider our maximum results limit? #234
Comments
Asking our users a good idea. I can ask on Twitter. FYI, FreeBMD has a max of 3000. |
@PatReynolds to send text to @DeniseColbert |
Sent draft 28 Feb 2022 |
@DeniseColbert to provide an image for SM with a screengrab of the Too Many Results message, then post to FB, @PatReynolds to post on Twitter |
Tweeted in Ancestry Hour 16 March 2022 |
Next (not immediate next) Vols newsletter, and re-tweet. |
Was in the Vols newsletter. Pat to tweet for Ancestry Hour on Tues 21st |
@DeniseColbert to put into next General Newsletter. |
There doesn't seem to be a demand, but @DeniseColbert to ask in a newsletter to check this. |
For October newsletter |
When we launched the Second generation of the apps we imposed a 250 limit on the number of results. This was done primarily as a means of limiting search run times. Since then we increased the limits to 500. There are about 4% of the searches still maxing out.
The efficiency of searches has been improved by the use of dedicated database servers and we have improved the index selection code such that there are few searches these days taking more than 10 seconds to complete and the vast majority are less than a second. Peoples computers have speeded up and their internet connections are now significantly faster than they were.
Should we increase the limit to 750 or even 1000? Should we ask the opinion of our users on this question? Personally I would not want to go through large lists
The text was updated successfully, but these errors were encountered: