Performance Issues
If users on large RAMP systems are experiencing delays the first time they go from one RAMP screen to another, it is possible that there are so many RAMP nodes in the session that the Find Path algorithm is having difficulty finding a path between the screens.
Developers of large RAMP-TS systems using Axes 3.1 can now use the alternative Find Path algorithm Find Path V2 which may solve this problem.
The symptoms of the problem are:
- This error appears on the end user's screen: "A script on this page is causing Internet Explorer to run slowly"
- In the application trace there is a long time gap between the time in the trace line "Find Path V1" and the next line in the trace.
The new algorithm is much faster, but may occasionally result in RAMP finding a different path between screens than it did with the old algorithm.
So thorough re-testing of the RAMP application is required if changing from one algorithm to the other.To activate Find Path V2 use this statement in your login script:
GLOBAL_bUseFindPathV2 = true;
In the application trace, the line "Using Find Path V1" or "Using Find Path V2" will indicate which algorithm is being used.