Visual LANSA Forum

Is there a correlation to debug performance and the number of generated Javascript files?

I have a VL Web app that has 40 application specific javascript files, this does NOT include the LANSA javascript files. All the web components are getting loaded at once.

I have noticed that debugging is pretty much impossible at this point I have waited for over 10 minutes for the page to rendered. When I debug my VLF-ONE app, the page is rendered much, much faster, normally within a minute or so.

As I was looking the through the scripts I noticed the number in my VL Web app is significantly higher then what is in my VLF-ONE app.

Normally its not a problem and I would debug the javascripts directly with the Chrome debugger, however I can't even debug my server modules because I can't get the page to load to invoke the modules.

So some questions:

1. Is it possible to disable debug of ALL web components so that only server components (Server Modules) are debugged?
2. Is there a correlation of debug performance to the number of javascript files loaded?
3. If there is a correlation, how do you reduce the number of scripts loaded? I assume you have to create the the script components dynamically using CREATE_FROM

So I know when you compile an object and the prompt window comes up with compile options, one of them is enable debugging.
Turning that off for your webpages/RPs and widgets might help with performance.
It will only go off for objects that have it on like your server mods.

I built a fairly hefty mobile app recently and I would say that debug did get a bit more boggy. It could be that my RPs are on the larger side vs the amount of them, but either way more of anything you could expect a performance hit
I'm not sure about how to reduce the number of scripts generated.

My friend, you are a genius.

I did not think to simply not enable "debug" on the compile of RPs and Web Pages.

That one small thing brings the page up in about a minute.

Thanks!
Joe

Edit
Well that worked a few times.
I also tried to Right Click all the RPs and select Debug -> Disable All and that did not seem to help either.

Edit
Either I wait or the Server Module break point does not get hit.

I saw that disable all recently and I don't think it worked for my VL-WIN stuff.

Even in test partition, I generally compile all objects as debug off and only recompile the one I want to debug.

I don't know if its different for VLWeb, but if I don't compile the RPs for debug, or if I use Debug -> Disable All on the RPs, then the break points on the Server Module does not catch, even after I recompile the Server Module WITH debug.

I was able to get it to work a couple times by compiling all the RPs without debug, then compile the RP that calls the Server Module with debug on. Now I can't get it to repeat. lol. ugh.

So i have a webpage that makes a call to one SVRMOD and I have an RP embedded into that webpage thats making a seperate call to another SVRMOD.

Web page that calls its SVRMOD, debug doesn't fire off (like it should)
My RP that calls its SVRMOD (which is the only obj with debug turned on) will break on its point in the server module.

So when compiling do you have compile only when necessary unchecked?
And where are your breakpoints in the SVRMOD? I put mine at the Srvroutine name(blablabla)

Maybe its something about your RP thats calling the SVRMOD?

I always have compile checked, never only if necessary.

The break point is placed on the first line in the srvroutine typically setting a status flag.

So your Web Page all your RPs are complied without debug right?

Yep, none of my RPs/Webapges have it enabled, just the SVRMODS.

Ok, so I finally got some consistency.

Right Click -> Debug -> Disable All seems to be the root of the issue. So I made sure that all the RPs were "debug enabled".

I then compiled all the RPs with debug OFF.

Then Right Click on the WP select Debug -> Start and after a brief wait the page is rendered and the SM break point is hit.

Let me run with this a bit and go from there.

Thanks for your help!