Support

Script Runs Slower Than Expected

2/21/07

 

Applies to:  FoxtrotOne, Foxtrot LE

Summary

Scripts seem to be running slower than expected. There are many factors that may make a once-speedy script run slowly.  The first step is to identify any recent changes to your environment. Look for:

 

New software installed

 

New hardware installed

 

Changes to your network configuration

 

Changes (updates/patches) to your PC operating system or to your host system etc.

NOTE:  Any change to the configuration of your PC, your emulator, your network or your host system may affect Foxtrot’s performance

Resolution

If you can track down a particular change (see "Cause"), see if reversing that change restores performance (i.e. uninstall "Bloatware Administration Plus for Networks 13.2" and see if speed improves.) If you cannot identify a specific change, review the points below. One or more may apply to your situation or may point you to practices and configurations that may improve performance.

 

  1. Large Database Size - The size of the database file is a factor that will cause a script to run slower.  The larger the size, the slower it will run. Split the database into smaller sections.
  2. Changing Operating System - "Upgrading" the operating system on a PC that has Windows 95 or 98 to Windows 2000, NT, or XP may drastically slow response time. Hardware upgrades to the PC (particularly increasing the amount of RAM) may improve performance.
  3. Overuse of the Pause Control Key - Frequent use of the "Pause" Control Key will slow down any script (that’s what it’s for, after all).  While some "Pauses" may be necessary to accommodate very slow or inconsistent host response (i.e. Check Screens fail occasionally) "Pause" should be used sparingly.  Review Foxtrot’s timing and running options for more ways to handle this situation, such as adjusting the delay interval for the "Run Script" speed control, or adding a "Wait Until Ready" Next Script
  4. Databases and Scripts Running across the Network - If scripts and databases are stored across a network, network latency and traffic may reduce performance or even cause errors.  Copy databases or script folders to the hard drive of the local PC to resolve this.
  5. Retry Check Screen & Retry Script Search - In "Tools/Options/Preferences".  If the "Retry Check Screen" option is selected, it may slow down the script. While this option may be necessary for some emulators, or for slow host response, the latest update of Foxtrot provides several options to fine-tune and enhance performance. Try the "Check for Redraw only" option, or reduce the "interval" between comparisons to improve speed.
  6. Unisys Enter - In "Tools/Options/Preferences".  For UNIX and Unisys hosts that require this option, reducing the retry time may speed up the script. Note that enhancements in this option in the latest release of Foxtrot will greatly enhance UNIX/Unisys performance.
  7. Changing Emulators - All emulators support Foxtrot differently; changing from one to another will effect how your script performs, and may even change how some Control Keys behave.  Some emulators can be up to twice as fast as others.
  8. Time of Day/Day of Month - In companies where there is a time-sensitive daily or monthly routine such as daily teller balancing or month end/quarterly reporting, at certain times of day or days of the month scripts may run significantly slower due to slower host system response.  A script that runs at 30 RPMs at 5:00 am on June 5 may run at 5 RPMs at 4:30 on Friday, June 30.
  9. Slow Network Connection - If you have a low-priority connection to your host, or your network is slow due to heavy traffic, Foxtrot scripts may also run slower.  This will be most apparent when you start Foxtrot: if it’s slow to start, there’s a good chance network performance is an issue.  To improve performance, reset your workstation preferences to use a local or departmental drive for "User and Machine" profiles, and see #3 above.
  10. Show Data Option "On" - When this option on the "Run Script" tab is selected, you can see the data being run in the Database Center. This option will slow performance. Once you are confident your script is running correctly, turning this option "off" to speed things up.
  11. Message Logging - In "Tool / Options / Workstation Setup".  This option allows the Foxtrot Administrator to view the status of all Foxtrot users in near-real-time, but, may drag performance especially if the network is slow.  Deselecting this option will improve speed.
  12. PC RAM - The more the better.  Any PC running less than twice it’s operating system’s recommended RAM can benefit dramatically from getting up to that level.  This upgrade is usually relatively inexpensive, and may add several years’ useful life to an older PC.
  13. Slow PC - While Foxtrot will run on PCs with clock speeds as low as 75 mHz, anything under 1 gHz is a clear candidate for an upgrade. Foxtrot can’t run any faster than your PC, so the faster it is, the faster Foxtrot can run.

 

 

arrowReturn to All Support Articles

 
In This Section: Article Search:
Please enter the phrase or keyword you wish to search for:

  
    
Automation Software and ServicesData Migration Case StudiesData Scripting Blog by EnableSoftPress ReleasesAbout EnableSoftContact EnableSoft
What is Foxtrot?Who Needs Foxtrot?Why Use Foxtrot?
Data Management Software Support Contact Enablesoft