We have a rather large application -- 110 screens at last count.
For several parts of this application the performance of the screens (response to touch events mainly) is quite good when the parts (consisting of 10 or so screens) are run stand-alone on a test driver.
But when integrated into the whole application response to individual touch events becomes sluggish -- like 1/3 of a second. Multiple button presses "stack up" and dribble out over several seconds, while drag events appear to be emitted at a much lower rate, such that much of the drag operation (and what little sensitivity/accuracy there was to begin with) is lost.
Note that this problem occurs even when only a few screens have been "visited" (and hence created) since application startup, so it's not like storage has been "clogged" by 100 screens. And the code involved isn't doing a whole lot of processing for each touch -- no file or resource file I/O (except maybe what the UI parts are accessing, but I didn't think that happens once the screen has been initially drawn), only creating a few string objects & updating labels, etc.
Has anyone got any ideas what could be causing this? Does anyone have any ideas on how to debug it? (It is, of course, difficult to tell much about the situation on the emulator.)