Form takes 5secs to load - solved

[JohanR]

Hi ,

I have a form that used to load blazingly fast and now takes 5 secs,

Attached is a pic to illustrate the time taken and below is a DEBUG log.

How can I get further info on these lines "[NetDLL] [2] CallBackWindowSrc() : NTThread Event : 523 start" to see what is slowing things down?

Are there additional debug switches to drill down or to get more info?

641   11:12:34.030   6644   xtvcweb.exe   [st] [netTalk][thread=3] p_web.OpenFile:zaq7
642   11:12:34.457   6644   xtvcweb.exe   [NetDLL] [2] CallBackWindowSrc() : NTThread Event : 523 start
643   11:12:34.457   6644   xtvcweb.exe   [NetDLL] [2] CallBackWindowSrc() : NTThread Event : 523 end
644   11:12:35.452   6644   xtvcweb.exe   [NetDLL] [2] CallBackWindowSrc() : NTThread Event : 523 start
645   11:12:35.452   6644   xtvcweb.exe   [NetDLL] [2] CallBackWindowSrc() : NTThread Event : 523 end
646   11:12:36.462   6644   xtvcweb.exe   [NetDLL] [2] CallBackWindowSrc() : NTThread Event : 523 start
647   11:12:36.462   6644   xtvcweb.exe   [NetDLL] [2] CallBackWindowSrc() : NTThread Event : 523 end
648   11:12:37.456   6644   xtvcweb.exe   [NetDLL] [2] CallBackWindowSrc() : NTThread Event : 523 start
649   11:12:37.456   6644   xtvcweb.exe   [NetDLL] [2] CallBackWindowSrc() : NTThread Event : 523 end
650   11:12:38.463   6644   xtvcweb.exe   [NetDLL] [2] CallBackWindowSrc() : NTThread Event : 523 start
651   11:12:38.464   6644   xtvcweb.exe   [NetDLL] [2] CallBackWindowSrc() : NTThread Event : 523 end
652   11:12:39.455   6644   xtvcweb.exe   [NetDLL] [2] CallBackWindowSrc() : NTThread Event : 523 start
653   11:12:39.455   6644   xtvcweb.exe   [NetDLL] [2] CallBackWindowSrc() : NTThread Event : 523 end
654   11:12:39.631   6644   xtvcweb.exe   ConfirmQuote_AAA_Start of Procedure Setup   4,035,964


thanks

Johan

[JohanR]

Hi,

OK,
I backtracked the last items I added to the form and removed one by one,
and found after removing a tab with a procedure on it solved it.

Will now try to see why that procedure caused the problem.

I did find quite a nifty recording function under the "Performance" tab in the devtools on Chrome.
Still figuring it out, but could prove useful in fine tuning performance


thanks

Johan