ListGrid connected to a DataSource

[skylerclooney]

I’m testing with a dataset of around 50,000 records. The ListGrid renders fine with smaller sets, but when I push it to tens of thousands of rows, things start to lag. I understand that loading everything at once isn’t practical, so I’ve been reading about paging, criteria filtering, and cache policies in the docs.

isc.DataSource.create({
    ID: "employeeDS",
    dataFormat: "json",
    fields: [
        {name: "id", primaryKey: true, type: "sequence"},
        {name: "name", type: "text"},
        {name: "department", type: "text"},
        {name: "salary", type: "integer"}
    ],
    dataURL: "/data/employees"
});

isc.ListGrid.create({
    ID: "employeeGrid",
    width: "100%",
    height: "100%",
    autoFetchData: true,
    dataSource: "employeeDS",
    showFilterEditor: true,
    canEdit: true,
    fields: [
        {name: "id"},
        {name: "name"},
        {name: "department"},
        {name: "salary"}
    ]
});

The grid loads correctly, but as soon as I push a large dataset through /data/employees, performance drops.
Should I be enabling paging explicitly to keep only part of the dataset in memory at a time?
Is it common to apply criteria filtering on the server side to only fetch what’s needed as users scroll?
Are there recommended cache settings or patterns that help balance responsiveness with not hammering the Pips NYT server?

[Isomorphic]

It looks like you may have skipped over the QuickStart and/or some of the other overview materials. Basically just read those.

Whether you use the SmartClient Server or use RestDataSource, everything is automatic and the default behavior represents the best practices.