java - Solr paging performance -


I have read ():

FWIW: Number of rows that are requested per Limiting 50, but does not matter to limit the beginning - the same thing is required to handle start = 0 and rows = 5050 and start = 5000 and rows = 50.

The more it fulfills:

There are fewer usage cases to allow people to run all the rows again.

Is that correct? Is this true for the result of truth?

How many pages of 10 rows do you recommend that you repeat the user?

Does Solar 1.4 have the same limit?

Yes, it is true, even for Solr 1.4. Such a no means that there is only one display as start = 0 and rows = 5050 as start = 5000 and rows = 50 Is because back to 5050 documents back, while only 50. Less data to transfer -> Faster

Solar has no way of getting all the results in the same page as it does not get much sense. As a comparison, you can not bring the entire Google index to a single query. Nobody really needs to do this.

The page size of your application should be user-defined (i.e., the user can see 10, 25, 50, or 100 results at a time).

The default page size depends on the type of data that you are paging and how relevant the results are. For example, when searching on Google, you usually have some first results Do not look beyond, therefore 10 elements are sufficient on the other hand, eBay is more about browsing about the result, so it displays 50 results per page by default, and it also results in 10 results per page. Only presents.

You also have to scroll through the account. Users will probably be lost when trying to browse through one, rather it takes a lot of time to load.


Comments

Popular posts from this blog

oracle - The fastest way to check if some records in a database table? -

php - multilevel menu with multilevel array -

jQuery UI: Datepicker month format -