html - Would iframes improve performance of sites with very large numbers of dom elements? -

html - Would iframes improve performance of sites with very large numbers of dom elements? -

for sites big numbers of dom elements, there performance benefit presenting of content within iframe? example, application i'm working on has big html-based tree contain tens of thousands of nodes @ 1 time (albeit not loaded @ once). putting aside usability problems tree size presents, there benefit placing content within iframe, rather within main page? browsers handle memory differently content embedded within iframes? improve jquery selector performance isolating content? i'm interested in how applied ie 7, although curious if differs between browsers.

+1 question. i'm not aware of differences in memory handling between frames , non-frames based content; i've written few xhtml parsers , memory memory; nodes take memory regardless of stored. id lookups done keys (hashtable), collections can quite big non-linear impact.

that's parsing , memory side; however, i've found rendering times can suffer on big innerhtml inserts, seek utilize document.createelement pattern instead (if applicable). experienced behavior in variety of browsers, including ie7.

where dom elements originate matters. nodes rendered server-side, or send json client , create tree in javascript? can confirm constructed javascript object trees can handle thousands of nodes efficiently, if rendering scheme client-based , nodes aren't displayed @ once, actual dom much smaller.

the real decision point round-tripping. if rebuilding complex page on , over, may justification plenty breaking out frames, content doesn't need sent on wire 1 time again , again.

html browser iframe