16.03.2016, 21:15
Vince mentioned exactly what you should do:
Instead of loading all the rows at once, you do it in parts. To achieve this, you spread the amount of rows loaded at once over an x amount of pages. The pro of doing it this way is that instead of loading all the rows at once, you have to load the amount of rows that fit on the page.
An example:
13,000 rows. Let us say that you can fit 20 rows on one page. 13,000/20 = 650 pages of data. For the first page you load the first 20 rows in the database. When the player goes to the second page you load another 20 rows and so forth.
EDIT: alternatively you could only load in the rows of the players that have been active in the timespan of a month or two months to lower the amount of rows that you should load.
Quote:
|
Originally Posted by Vince
 That's why pagination was invented.
|
An example:
13,000 rows. Let us say that you can fit 20 rows on one page. 13,000/20 = 650 pages of data. For the first page you load the first 20 rows in the database. When the player goes to the second page you load another 20 rows and so forth.
EDIT: alternatively you could only load in the rows of the players that have been active in the timespan of a month or two months to lower the amount of rows that you should load.