I experienced two performance issues with dhtmlxGrid.
with either smart-rendering or paging, the filter works very slow for data set of 50,000+ rows. Typically it takes a few minutes to show up the filtered rows and this frustrates the users.
when there are many columns ( 200+ columns) in a dhtmlxGrid, the IE often freezes. FireFox is more stable. Is there some way to help improving this problem? 200+ columns in a grid apparently is not good practice, but it’s what the users are using.
By the way, in our existing code, I notice a line
mygrid.enableSmartRendering(false,500)
What would the second para do when the first para is ‘false’?
Are you using client side or server side filters?
Client side filters are not purposed for such big datasets.
Server side filters must work fast enough if dynamic loading mode is used.
Grid data optimization is done against big count of the rows. Big count of columns will slowdown grid in any mode. Using smart-rendering will help a bit, but still can’t be counted as solution.
Decreasing count of columns is only way to improve overall performance.
mygrid.enableSmartRendering(false,500)
It sending a size of loading buffer, but because of “false” as first parameter - it will never be used
I am doing client-side filtering. Is there a filter mode called ‘server_search’? I saw it in our existing source code everything but don’t find it in your list ‘text_filter’, ‘combo_filter’, ‘text_search’ … Is the ‘server_search’ a deppreciated feature? Or it’s just that our previous developer thought this as the way to do server-side search/filter?
I guess i will have to tell the users not to put too many columns there.
There is no such filtering mode as “server_search” , but grid allows to define custom filtering modes - so it can be a some custom mode, which was added on your side.