Is smartclient suitable?

Question

How does SmartClient timeout scale for thousands of users edit grids?

I got warnings before ExtJS is not suitable.

Answer 1

SmartClient has one grid component that performs both horizontal and vertical incremental rendering, so it processes a very large number of two rows (several million) and columns (several hundred) without sacrificing performance.

All grid functions supported by SmartClient - built-in editing, grouping, filtering, dynamic frozen columns, sorting, reordering fields, drag and drop. (list too long) is supported by this single component of the large data grid.

Several users have encountered scalability issues with the Ext grid component and discussed it here on the SmartClient forums:

http://forums.smartclient.com/showthread.php?t=2678

Regarding server scalability, in fact, the grid component greatly affects server-side scalability. Consider the adaptive SmartClient mesh filtering mechanism:

http://www.smartclient.com/index.jsp#adaptiveFilter

This function and the related function "Adaptive Sorting" reduce 60-90% of the most expensive types of server calls (that is, those that access and filter / sort a large data set).

SmartClient makes extensive use of this intelligent data reuse approach to avoid costly server-side operations. A good overview is available in the ResultSet class documentation; ResultSet is used as a cache management object for all components that work with data sets in SmartClient:

http://www.smartclient.com/docs/9.0/a/b/c/go.html#class..ResultSet

Answer 2

The number of user editing grids does not really matter - it is more a question of how your application is designed to support downloads. If you ask a question about performance compared to the grid component, the most important questions concern the capabilities of the grid and the amount of data that can be processed, and not how many users will use it over time.

I am not familiar with SmartClient, but in the case of Ext, the grid works very well for small and medium grid data (up to about 50 rows per page, up to ~ 10 columns of data). Obviously, this all depends on many variables, but it’s true that the ext grid rendering time increases in proportion to the amount of data transferred at one time. This is due to the fact that it uses a rather heavy DOM under covers, a compromise is a rich set of functions and flexibility, which is for creating custom layouts of nested lines. It supports paging to mitigate performance issues, and there is a very popular extension that provides on-demand line loading (virtual scrolling), which allows higher loading of large data sets. There's also an example of a lighter and simpler version of buffered loading in Ext examples that show excellent performance with lots of data.

In addition, depending on your needs, there is a new lightweight ListView in 3.0. It does not support all the features of the GridView, but if you only need a screen mesh in the first place, this can be a great alternative.

All this does not mean that SmartClient is not very good - I have no idea. I just want someone to look at this topic to get an informed decision regarding the outside of the equation, because it sounds like you got one-sided opinions on this.

Answer 3

Thank you for your reply. I got the impression that the average Joe entering the website with Ext would be discouraged when he had to deal with long loading times, which also increased if there were a lot of people on the website. It was for this reason that I thought SmartClient would be better, but I did not find any comparison between the two. Maybe I was in a hurry, ignoring ExtJS.

I will hope to get in touch with someone who has had SmartClient experience to help develop my future site. thanks hedgehog