I'm not really surprised, given all the issues we know of, including event leaks and poor GC behavior. Did we get the profiler running in DHTML yet?
I'd propose that you spend time building and running benchmarks across the SWF runtime and IE/non IE dhtml: * Tucker's javascript performance test suite * Node instantiation/destruction * View instantiation/destruction * Time to copy a fixed set of xml nodes to dataelements * Etech demo startup time broken across: initialization. data load. data copy, first screen initialization. Comparing the numbers with trunk will give us an idea of where things have slowed down in legals. As a second pass, looking at memory usage would be nice. This will help us gage where the time is going and where we need to focus efforts to improve performance. Let me know your thoughts! -- Regards, Max Carlson OpenLaszlo.org Henry Minsky wrote: > I ran the LZPIX app in IE6 with the task manager open showing the amount > of RAM allocated to the > iexplorer.exe process. Every time I click on a thumbnail to display it, > it eats about 2 MB of RAM, which > never is released. In Firefox, it consumes a much smaller amount, maybe > 1-200k which gets GC'd the next thumbnail I click on. > > I am going to try to figure out if this is the XML data load eating all > that memory, or what... > > > > > > _______________________________________________ Laszlo-dev mailing list [email protected] http://www.openlaszlo.org/mailman/listinfo/laszlo-dev
