How many records are returned to populate the grid?  If it’s taking 5+ minutes 
to complete, then the number of records, the table or query optimization is 
probably the more important issue.    I would suggest the following:

1) Implement a paging solution with OFFSET/LIMIT - You can use AJAX to page the 
results.
2) Optimize your SELECT statement to ensure that the the JSON object produced 
is as fast as possible.
3) If you’re using a web service, over which you have no control of the number 
of records returned in the query, then implement a two-phase approach to first 
pull the data and cache it locally with a time out (file-based or database, 
your call), then manipulate the records via the above suggestions.  Your 
request flow could show a “Fetching Results” with a .complete() event to handle 
running a new function to populate the grid when the local AJAX request returns 
the 200.

HTH,
Jon


On Jun 14, 2014, at 10:16 AM, John M Bliss <[email protected]> wrote:

> 
> Hi!
> 
> So I added this code to increase our EXT grid timeout from 2.5 minutes to
> 10 minutes:
> 
> Ext.onReady(function(){
>    Ext.Ajax.timeout = 600000;
> });
> 
> So now, EXT grids will wait longer for CF to return the JSON to populate
> the grids. Works great under about 5 minutes. The problem is: *above* 5
> minutes, when the request for the JSON finally finishes (I can see this
> happening via FusionReactor), the grid's "spinner" just keeps spinning.
> Like it's no longer listening for the JSON request to complete.
> 
> Any ideas?
> 
> -- 
> John Bliss - http://www.linkedin.com/in/jbliss
> 
> 
> 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Order the Adobe Coldfusion Anthology now!
http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion
Archive: 
http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:358738
Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm

Reply via email to