Have you run this in the profiler? It
might highlight code that’s running more often than you’d think it
should. Also I wonder if the non-responsive time is due to garbage
collection, have you watched the task manager while the app is unresponsive
(not that we really release that memory to the OS)? The fact that the
time increases based on the references certainly makes it seem like a potential
memory management issue.
Don’t have any other real ideas and
don’t really have time to run the tests myself, sorry!
Matt
Hi Matt,
I have read
(and now re-read) your excellent large data articles
(which are
now well established within the Flex literature's cannon).
This
exercise was an attempt to squeeze all the performance out of our
requests
before we implement paging and to try to establish an optimum
page
size. I wanted to try to make some addtional improvements
because I
was afraid that (assuming performance declined linearly)
loading
small chunks of data would still make that application to
unresponsive.
This seems to be a poor assumption in the case of our
actual
problem.
I'm still
curious as to why deserialization performance decreases
non-linearly
with item count (but not item size), why common object
references
affect the load time, or why there is a significant period
*after* the
resultHandler during which the client becomes
unresponsive.
Any help with these questions would help set my mind at
ease.
Thanks,
Alex
Yahoo! Groups Links
|
