3

i'm working with backend and having around 100k records in the table. The problem is, when im loading this list, request times out because it takes longer than 30 seconds to load and also if it manages to load (increasing timeout) the list is not separated to pages, just whole list of records on the one page.

Has anyone ever encountered this issue and is there a way to fix this bug?

Ivan Zhivolupov
  • 1,107
  • 2
  • 20
  • 39
  • 2
    Have you got something like `recordsPerPage: 25` in your `config_list.yaml` ? I noticed when using the builder plugin it doesn't add it automatically. – Joseph Jun 29 '17 at 14:58
  • @Joseph Hello, thank you for fast reply. This line is there, so this is why i've decided to come here. This was the first thing i've checked – Ivan Zhivolupov Jun 29 '17 at 14:58
  • I can't think what could be causing that on a default setup -- an absence of a db index could make it timeout but not show the whole list like that -- but if you've done anything custom then I guess post the full controller and yaml code and maybe I (or someone else) will notice something. – Joseph Jun 29 '17 at 16:27
  • @Joseph Thank you for spending time on that, i've decided to disable functionality to view this database table and to create a search page instead so i can go directly to the entry – Ivan Zhivolupov Jun 29 '17 at 17:50

1 Answers1

1

Sounds like you may need to enable pagination on your list. Open the list_config.yaml configuration file found in your controller directory and check for the recordsPerPage option:

# ===================================
#  List Behavior Config
# ===================================

# ...

# Records to display per page
recordsPerPage: 20
Samuel Georges
  • 973
  • 4
  • 7