Hello,
here a rudimentary test of how a pure client-server Uniface10 application works. The test values are also consistent with Uniface9. The seconds mentioned are just for comparative purpose and indicate the start/load time of the application (no database accesses).
Uniface is processing on the client (no Anywhere etc., which indeed would solve this problem).
The application used has some 500 forms and services, so not that large uar-file for the application.
Uniface = the interpreter (that is installed as you execute eg. swinuf10402011w32.exe)
Application = the uar-file containing the application forms, messages etc. + ini + asn + images etc.
Locally = installed locally on client PC/Laptop
Only Uniface locally Uniface+Application on shared Drive Uniface+Application locally
Virusscan on client 4 sec 15 sec 4 sec
No virusscan 3 sec 10 sec 3 sec
Vpn with virusscan 15 sec 180 sec 8 sec
Vpn no virusscan 10 sec 90 sec 7 sec
I'm most intrested in the bad response time executing Uniface over VPN as Uniface is installed on the shared network drive.
There seem to be no severe problem to have the Application on the shared network drive, but Uniface itself seem to be the problem.
Very much is happening starting Uniface, which probably isn't good using eg. a VPN connection. I can't say that much about the speed of the Vpn connection but it shouldn't be that bad, ie. the test results are a bit surprising.
What makes Uniface (the interpreter) so slow loading itself over Vpn?
Are there anything one can do/try expect installing Uniface locally on all clients? And yes I know that Uniface recommends installing Uniface locally.
Any comment appreciated?
Regards RogerW
------------------------------
Roger Wallin
Abilita Oy
------------------------------



