Page 1 of 1

Debugging slow processing

Posted: Sat Dec 28, 2013 7:33 am
by cusingerBUSCw5N
My app is very slow going to the main card. I turned on Message Watcher and found that when I go from a card to the main card, it takes 7 seconds before it reports any message - and then it reports that it's doing something with dgProps

Then it takes another 3 to 6 seconds and then reports suspendStack followed by cRevTable, followed by focusOut
(it does a lot of other things, but the timing for those seem to be negligible).

Bottom line - is it takes 10 to 13 seconds to go load the card.

How should I go about fixing this? Is it because there are too many fields? that I'm using some groups? I find that if I eliminate all the script for that card, it is STILL just as slow - so something's happening behind the scenes. That card isn't hitting the database, so I don't think that is the cause...

It also seems to start a new list with Message Watcher - versus when I go from the main page to another page, Message Watcher just continues...

Any ideas would be appreciated.

Re: Debugging slow processing

Posted: Sat Dec 28, 2013 8:42 am
by SparkOut
No way of really telling, but just a thought...
Do you have any hidden fields on the main card? If so, have you stored any binary data in there (eg a file you store for portabilty to be written out and later executed)? That can really slow things down as the engine still tries to make sense of the rendering, even for a hidden field. Store binary data in a custom property instead if this is the case. If not, I guess other people may have some suggestions, but I think more script detail from the main card is needed.