# Discover - eager loading **URL:** \ **Category:** Kibana\ **Created:** [March 24, 2023, 12:13pm UTC](https://discuss.elastic.co/t/discover-eager-loading/328458 "2023-03-24T12:13:38Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Kamil\_Zielinski](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kamil_zielinski/32/118886_2.png) [@Kamil\_Zielinski](https://discuss.elastic.co/u/Kamil_Zielinski)\ **Post date:** [March 24, 2023, 12:13pm UTC](https://discuss.elastic.co/t/discover-eager-loading/328458/1 "2023-03-24T12:13:38Z")
Hey, Is there a way to enable the eager loading of the logs in the Kibana/Discovery tab? I'm using Kibana 8.6v. Currently, When I type some query into the Discover search box I get around 400 rows with various JSONs. And while I'm scrolling Kibana lazy loads the next logs/jsons. The drawback of it is that I can't use browser search on the resulting rows as they are being changed and Chrome doesn't indexes them (indexes only visible ones). The preferred way would be to get and present all rows at once (mentioned 400). I do understand that it may impact browser performance but currently, it take me more time to reload and scroll all over again to find what I want in my logs. Is there a way to achieve that ? Kind Regards, Kamil ---
**Author:** ![bhavyarm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bhavyarm/32/22392_2.png) [@bhavyarm](https://discuss.elastic.co/u/bhavyarm)\ **Post date:** [March 24, 2023, 8:28pm UTC](https://discuss.elastic.co/t/discover-eager-loading/328458/2 "2023-03-24T20:28:00Z")
Hi, You have two things which might help. You can set rows per page - ![Screen Shot 2023-03-24 at 4.25.07 PM](https://us1.discourse-cdn.com/elastic/original/3X/f/4/f440aab0596ce7bda3163f4ce2c401e0d1d06f32.jpeg) You can also go to advanced settings under management and set maximum rows per table ![Screen Shot 2023-03-24 at 4.27.38 PM](https://us1.discourse-cdn.com/elastic/original/3X/b/1/b10af05f34c240bfaa6ba79d0a103c4d7f54e5a2.jpeg) Thanks, Bhavya ---
**Author:** ![Kamil\_Zielinski](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kamil_zielinski/32/118886_2.png) [@Kamil\_Zielinski](https://discuss.elastic.co/u/Kamil_Zielinski)\ **Post date:** [March 27, 2023, 1:30pm UTC](https://discuss.elastic.co/t/discover-eager-loading/328458/3 "2023-03-27T13:30:28Z")
We already have set these two settings to 500 but it still lazy loads rows. I switched back to legacy Document Viewer and it seems to work much much better (at least once it loads all logs, it keeps them - not like this new viewer which removes them) ---
**Author:** ![Davis\_McPhee](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davis_mcphee/32/112461_2.png) [@Davis\_McPhee](https://discuss.elastic.co/u/Davis_McPhee)\ **Post date:** [March 27, 2023, 3:56pm UTC](https://discuss.elastic.co/t/discover-eager-loading/328458/4 "2023-03-27T15:56:46Z")
@Kamil_Zielinski Thanks for bringing this to our attention. As you noted, this is done for performance reasons and is actually the result of the virtualization feature of the data grid component we're using in Discover: [https://elastic.github.io/eui/#/tabular-content/data-grid#virtualization](https://elastic.github.io/eui/#/tabular-content/data-grid#virtualization). Currently this can't be disabled, and unfortunately I don't have a good workaround to suggest apart from switching to the classic table as you did, refining the overall search to only the results you're interested in, or exporting a CSV report from the "Share" menu and searching within that. Thanks again for bringing this up so the team is aware that it's a potential area for improvement with the new data grid. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 24, 2023, 3:57pm UTC](https://discuss.elastic.co/t/discover-eager-loading/328458/5 "2023-04-24T15:57:02Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.