Hmm, nothing strikes me. A 1200 row table shouldn't be that big of a deal (couple of seconds to render maybe depending on table and cell data sizes, but then it should all be good), unless maybe you're attaching event handlers to every row/cell/element or something like that upon render, in which case I'd say employ a lazy loading technique to delay event wiring until the last possible moment, depending on the event. Investigate how many actual objects you're creating in memory during each stage of the request/render sequence (remember event handlers take memory too)... try to eliminate anything unnecessary. And also, is this happening the first time the data is loaded or only during subsequent requests (in which case I'd say you have a memory leak to sniff out)? So many things to think about :-)

Of course 1200 rows x 30+ columns x 1kb data per cell would be big... lol. You may just have to resort to paging your data (although I'm assuming this option has already been discussed and for whatever reason there is a requirement that all 1200+ rows be served at a time).

It's just hard to say what your problem is without seeing something. I mean, it could even be your machine or network for all we know.

Anyway, sorry I have nothing more profound to say than that...

On 9/6/06, ringerce <[EMAIL PROTECTED]> wrote:

Well, the problem with that is that the application that I'm building
is mean't for internal use only and it would be against my companies
policies to make it public. I'm really not doing anything outside of
the box here. My page does return a lot of html and I think the browser
just runs out of memory. It seems to crash when the DOM parser comes
into play.

Here is the function I wrote though to update my container. Maybe
you'll see something unusual:

function ajaxUpdater(mForm,mUrl,mMethod,outputObj) {
        var params = '';
        if(mForm) {
        params=customSerializer(mForm)+'&time='+currentTime();
        } else { params = '?time=' + currentTime(); }
        var ajax = new Ajax.Updater({
                success: outputObj},mUrl,{
                evalScripts:true, method: mMethod, parameters: params,
                onFailure: function(response) {
                        reportError( response.responseText);
                }
        });
}

------------------------------------------------------------------------------------------
and I call it like so
------------------------------------------------------------------------------------------
ajaxUpdater('','viewer.asp','get','contentPanel');
------------------------------------------------------------------------------------------
Pretty simple. Lemme know if you spot anything unusual.


Athena Group, Inc.
Inquire: 1-888-919-8700 x2903
Blog: http://www.someElement.com
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs
-~----------~----~----~----~------~----~------~--~---

Reply via email to