We are running WR 7.5 through Citrix. Till last week we didn't face any problem. It was running smoothly & the performance was good.
But suddenly from this week WR has gone too slow. Especially the file io operations like (file_open/file_getline) is taking lots of time to execute. Previously to read a simple file with 5 lines, used to take less than 10 seconds. The same is now taking 1 Minute.
The free space in the citrix server is 219MB.
Have anyone encountered this kind of problem before.
Make sure that all files you reference are on the citrix machine. Make sure your wrun.ini file is on a fast network location. Citrix copies this file to a user location. So if your Y:\ drive is your user network location than there is a wrun.ini on this drive. If there is slow traffic from the citrix server where winrunner is running to this ini file you will have very slow performance.
Don't load any modules and create just one testscript to see if you encounter the same problems
Answer to the questions you people have asked:
Q1. Try to figure out what was not there on server when it was running fine.
Ans: Unfortunatly unable to figure that out as it is not under my control
Q2. What are the addins?
Ans: Only VB addin
Q3. Is all files you reference are on the citrix machine?
If I run a simple script and perform file io it runs fine. No performance problems.
The WR project that I am running contains around 8 compiled modules. Also it loads around 90 lines into an array. While loading the modules/arrays itself WR performance issue starts. It has do something with the arrays that I suspect.
Will it be also because of:
a. Amount of Free Disk Space (which is currently 220 MB)
b. Any thing related to the memory.
1. Changed the Run Settings to 10 Milliseconds to the Delay & TimeOut settings on the Run Tab & Advanced Tab
2. Cleared the Arrays after use
3. Used dos_system command to create file instead of file_open & file_printf
But I still couldn't figure out why the same script, which was running fine before suddenly slowed down. My guess is someone should have fiddled around with the memory(cache/virtual memory etc.).