[CLOSED] Binding Large Set of Data to a Grid makes browser unresponsive

  1. #1

    [CLOSED] Binding Large Set of Data to a Grid makes browser unresponsive

    Hi,

    We have used Coolite Grid in our Web Application, when the output result from stored procedure is nearly 3000 rows there is no issue, when the resulted rows are closely 10000 then we receive a warning message as given below

    Click image for larger version. 

Name:	IE Error.jpg 
Views:	182 
Size:	21.3 KB 
ID:	1877

    Kindly help me on this. This error comes even when i bind to a coolite grid even without any Styles/Themes/Render Functions
    Last edited by Daniil; Nov 16, 2010 at 3:46 PM. Reason: [CLOSED]
  2. #2
    Hi,

    10000 is too many for browser (at least for IE).

    Using server side paging is only one way to resolve it.

    Please see the following examples:
    https://examples1.ext.net/#/GridPanel/..._Sorting/Page/
    https://examples1.ext.net/#/GridPanel/...ON_WebService/
    https://examples1.ext.net/#/GridPanel/...ML_WebService/
    https://examples1.ext.net/#/GridPanel/...rting/Handler/
  3. #3

    Binding Large Set of Data to a Grid makes browser unresponsive

    Hi Daniil:

    You mean to say that, when each time the user clicks on Page Navigation button we need to Execute the Stored Procedure which will return 10000 records and then display the records between (1 to 20) or depends upon the page and grid rows that is set right ?.

    See the Store Procedure will take atleast 30 seconds to produce the output, then applying condition 10 seconds and then binding 5 seconds, then to view each page records a user has to wait atleast 45 seconds, i dont know any client will accept this kind of processing right ?, also storing this data in a session or cookies is not fair.

    I hope you will be having a better solution, which will help us to give a better performance to the client.

    Quote Originally Posted by Daniil View Post
    Hi,

    10000 is too many for browser (at least for IE).

    Using server side paging is only one way to resolve it.

    Please see the following examples:
    https://examples1.ext.net/#/GridPanel/..._Sorting/Page/
    https://examples1.ext.net/#/GridPanel/...ON_WebService/
    https://examples1.ext.net/#/GridPanel/...ML_WebService/
    https://examples1.ext.net/#/GridPanel/...rting/Handler/
  4. #4
    Quote Originally Posted by speedstepmem3 View Post
    Hi Daniil:

    You mean to say that, when each time the user clicks on Page Navigation button we need to Execute the Stored Procedure which will return 10000 records and then display the records between (1 to 20) or depends upon the page and grid rows that is set right ?.
    The server side paging means that clicking on navigation buttons causes request to a server. You have to retrieve number of rows equal PagingToolbar's PageSize.

    Please investigate the examples that I mentioned.

    See also
    http://dev.sencha.com/deploy/dev/doc....PagingToolbar
  5. #5

    Binding Large Set of Data to a Grid makes browser unresponsive

    Hi Daniil:

    You guys think smart, but my question is that for the Server side paging, again i have to fetch the data from SP, bind it and then display number of rows equal PagingToolbar's PageSize right ?

    I hope you will be having a better solution, which will help us to give a better performance to the client.

    I just want to take data at one shot, but binding should be partiall, or else a client side paging is necessary


    Quote Originally Posted by Daniil View Post
    The server side paging means that clicking on navigation buttons causes request to a server. You have to retrieve number of rows equal PagingToolbar's PageSize.

    Please investigate the examples that I mentioned.

    See also
    http://dev.sencha.com/deploy/dev/doc....PagingToolbar
  6. #6
    Hi,

    First, you have to modify SP to return requested data only (do not return all 10000 records but just current grid page, current grid page is determined by start and limit params). After that you have to add proxy to the store because remote paging works with proxy only (it can be PageProxy or HttpProxy).

    Daniil mentioned about the examples which demonstrate that technic.
    Also please investigate the following article
    http://ext-net.blogspot.com/2010/11/...nst-large.html
    http://ext-net.blogspot.com/2010/11/...in-stored.html
  7. #7

    Same issue with performance in Grid

    Hi,I have around 10k Records in the Grid.Please let me know how to handle server side coding to handle multiple pages with Huge data.
    Please get me some Example if possible.I am using Version 1.0.Is i have to add any plug ins to support the same?

    Regards,
    Honne
  8. #8
    The one way we can suggest - remote paging. Please review the examples in the post #2 of the current thread.

Similar Threads

  1. Ext cache large data
    By huathaiphong in forum 1.x Help
    Replies: 2
    Last Post: May 24, 2012, 11:03 AM
  2. Replies: 4
    Last Post: Nov 22, 2010, 12:54 PM
  3. [CLOSED] Grid Panel Filter and Sorting futures for Large data
    By speedstepmem3 in forum 1.x Legacy Premium Help
    Replies: 1
    Last Post: May 16, 2010, 7:50 PM
  4. [CLOSED] GridPanel Loading with Large Data Set
    By bethc in forum 1.x Legacy Premium Help
    Replies: 3
    Last Post: Oct 28, 2009, 2:20 PM
  5. [CLOSED] Combobox makes page with large image really slow
    By jchau in forum 1.x Legacy Premium Help
    Replies: 8
    Last Post: Jun 10, 2009, 4:06 AM

Posting Permissions