We would like to reduce the webView chargetime. We make some test with a panel with 6 webViews and here the results.
"load" function used to call url in each webView.
Internal domain http web called in each webView.
Panel opened on server GEDI: Takes 9 seconds to charge completly
Panel opened on DesktopUI: Takes 30 seconds to charge completly
Any sugestion to improve it? Its annoying it takes so long
We use v17 P12
If you open the same URL in a browser window do you see longer loading times at the client where the Desktop UI is running?
How long is the loading time if you run a Desktop UI at the server (where you have started the GEDI)?
You can possibly do a speed test to check the connection speed for the server and the client.
Senior Support Specialist
We did some tests and we discarted a network problem: same chargetime took on a DesktopUI client in the same subnet, than in any other subnet.
Clarify that all managers incluiding http server are in the same server. We haven't a distributed setup.
About loading times, running a DesktopUI at the server, it charges the webViews much faster (8s) than with an external client Desktop UI (30s).
We tests the ULC UX client too, in the own server and in an external client. And in both cases it charges webViews in 8s. So the slow charge only happends in an external DesktopUI. No matter which network.
webViews loading time test result.
Any external DesktopUI client: 30s
DesktopUI in own server: 8s
External ULC UX client: 8s
ULC UX in own server: 8s
Any idea why only happends in an external DesktopUI ?
Here our http server config entries:
uiArguments = "-p vision/login.pnl -centered - iconBar -menuBar -ssa"
httpAuth = 1
httpsPort = 443
httpPort = 0
clientSideAuth = 0
httpServer = "https://localhost:443"
That does sound like caching issues. Your desktop UI is not having the pages in cache probably, thus the longer loading time. Nothing to really do with Desktop UI I am afraid. GEDI machine, being not wiped, is having them in cache.
Try to investigate where the navigation data are stored and try to add this folder to the sync for desktop UI, it may help (no guarantee).
BTW one very important missing test is : on the remote desktop UI machine, try to load the page inside a web browser, not in WinCC OA. So you can see the time (try also to clean cookies first to be clean).
In the same external client, web browser (cookies cleaned) loads instantly the webviews urls, only an external DesktopUI takes so long.
I don't think that its a caching issues, wich difference can there be between using a DesktopUI in an external machine than using a DesktopUI in the server machine?
Maybe, the http server works diferent with a DesktopUI client in the same machine (localhost) than with an external DesktopUI clients to charge webviews url?
Also remember that ULC UX charges webviews fine in both sides (external machine client and in the own server machine), its pretty weird to undestand.
In case of the Desktop-UI project data is loaded to the client machine and the UI process is running at the client machine. When ULC UX is used the UI is running at the machine where the CTRL manager (webclient_http.ctl) is started and only graphical information is transferred to the browser on the client.
Possibly the network between the server and the client is slow and therefore the startup of the Desktop UI at the client takes longer.
Senior Support Specialist