Hi Unifacers,

Since U7 Uniface enable to save all components on a server where Userver is running: UServer is acting in this case as File Server. Windows clients load all components through Userver when needed. This is accomplished with assignments like:

*.frm $TCP:...

After migrating to U97 with Standard Deployment (No UAR, just the directory tree!) the whole application is sensibly slower than before because of the single network round trip requested to load each specific Central Objects like Central Messages, Central Procs, and so on. On crowded networks the situation is now almost NOT acceptable.

We strongly feel this is a bug...

Request: Uniface runtime from U97 onwards when asking to an UServer, acting as File Server, for a basic component executable (like *.aps, *.frm, *.svc, *.rpt, ...) should be enabled to receive in a single network roundtrip all static objects being involved into execution of that basic component and UServer when defined for such functionality should be definable with a much much larger file system cache.

Regards,
Gianni

Hi Unifacers,

Since U7 Uniface enable to save all components on a server where Userver is running: UServer is acting in this case as File Server. Windows clients load all components through Userver when needed. This is accomplished with assignments like:

*.frm $TCP:...

After migrating to U97 with Standard Deployment (No UAR, just the directory tree!) the whole application is sensibly slower than before because of the single network round trip requested to load each specific Central Objects like Central Messages, Central Procs, and so on. On crowded networks the situation is now almost NOT acceptable.

We strongly feel this is a bug...

Request: Uniface runtime from U97 onwards when asking to an UServer, acting as File Server, for a basic component executable (like *.aps, *.frm, *.svc, *.rpt, ...) should be enabled to receive in a single network roundtrip all static objects being involved into execution of that basic component and UServer when defined for such functionality should be definable with a much much larger file system cache.

Regards,
Gianni

Hi Gianni

There one high priority issue we are currently working on:

Issue 32161  —   Bad performance in deployment when accessing an uar file via TCP network

https://u.uniface.info/fixes/issuelist/32161.php

Hope to have a fix in patch 46 or earlier.

There is an asn setting $memory.

You can try $memory zip=all. 

The mentioned issue is probably what most affects you.

Regards

Peter

Hi Gianni

There one high priority issue we are currently working on:

Issue 32161  —   Bad performance in deployment when accessing an uar file via TCP network

https://u.uniface.info/fixes/issuelist/32161.php

Hope to have a fix in patch 46 or earlier.

There is an asn setting $memory.

You can try $memory zip=all. 

The mentioned issue is probably what most affects you.

Regards

Peter