steps to reproduce

1. run the attached example
2. comparing 2 API usages to sort

result

To sort data with notifying change manually take less time and produce smaller response size.

        sortingRange.setAutoRefresh(false);
        sortingRange.sort(index, false, SortDataOption.NORMAL_DEFAULT, null, true, SortDataOption.NORMAL_DEFAULT, null, true, SortDataOption.NORMAL_DEFAULT, false, true, false);
        sortingRange.notifyChange();

expected result

since users don't call Range API multiple times, it seems ZSS can optimize this case for users.

debug info

• sortNotify.cpuprofile - profile result using notifyChange()
• the case with nofityChange() runs faster than the case without it.

with notifyChange() - 734.1ms

without notifyChange() - 1.43s