ringerce 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.
>
>
>
So, have you tried just loading up the data in its own page? Rendering a
big table taxes the brower - especially IE. That would give you
something to compare it with. Also, look at your table code - it should
render faster with explicit column widths. I had to troubleshoot a
similar problem recently where it turns out a customer was sending 5MB
of html tables over the wire and it was freezing up the browser for
minutes at a time. That code also happened to have inline event handlers
(onmouseover etc) in it. (I actually tried removing those and using a
single event handler and event.target filtering to get the same effect,
bit counter-intuitively it didnt really have much effect on overall
performance.)
With large amounts of data, every little inefficiency is magnified - so
check all your tags are closed properly, remove unnecessary markup,
validate etc.
> var ajax = new Ajax.Updater({
> success: outputObj},mUrl,{
> evalScripts:true, method: mMethod, parameters: params,
> onFailure: function(response) {
> reportError(response.responseText);
> }
>
>
Are you actually sending script along with this data? If not, set
evalScripts: false and you should see a big speed up.
Oh, and check with a fresh browser each time, and keep any eye on your
task manager / CPU - if you are leaking memory anywhere, your testing
can be skewed by previous versions of the page having crippled your
browser.
Another thing: debugging. If you are writing debug statements to the
same DOM you are trying to measure performance with its going to slow
down. Even console.log in Firebug drags appreciably.
I've also found that render time and network latency arent as seperate
as youd like them to be. If latency increases, overall performance can
decrease in a non-linear way.
hth
Sam (-i-am)
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
