My understanding is that the component is still in development, so hopefully there is a solution for this.  For now though, I do not think there is.  This data grid (as well as the advanced data grid for traditional web) loads all the data into the grid in its initial state.  I'm impressed that it was able to load 100k records for you, because that is actually quite a bit, considering they all need to be in memory.

Personally, I think the best solution for this is the ability to do server-side filtering in the columns.  This way, column filtering (and the other powerful features of the component) could still be used while not needing to load all the data into memory at the beginning.

Hello Somesh,

Currently the data grid need to receive all data to the client to be able to execute the functions like filter, sort and group without round trips to the server.

We are considering to add the ability to do some of these operations server side.

Can you please let us know what kind of functionalities you need in the grid, if you have the possibility to use server side? Is is pagination, filtering, sorting? What about grouping?

Thanks,

Bruno Martinho

Hi

Sorry, If I misunderstanding your issue.

First, I don't think loading Million+ records on a Screen is a good idea. What is the use case for this? 

Second, What is the original data source in this case? If you can control it(Access, Filter etc), You can expose an API. In the API to access the original datasource and fetch the smaller recordset you needed, then return it to the screen.

Furthermore, If possible you can implements API that supports pagination such as(e.g: top, skip )

Kind Regards

Hi Somesh,

This is not the right approach. Showing these many records in Datagrid would be a huge performance issue. Dont show more than 500 records in  a page

1. Show Pagination and the pagination should be server side . So for an example you are showing 100 records in a page than only 100 records should be send to Client Side (Sending all the record to client side would hang the browser)

2.Don't  fetch all the records in server side only fetch a single page result from DB. Keeping millions of item in server memory (RAM) would cause huge issue in high concurrency.

Best Regards

Devendra BAghel