I’m working on a project that has around 300 function libraries. They’re all located on the C drive of the automation host. Those libraries used to be associated "statically" to each test (we don’t do this manually, of course, we use Test Design Studio). We’re currently trying to move away from that approach and associate everything dynamically with LoadFunctionLibrary. The first thing we tried was to load all libraries at one time (sort of like creating a huge include file). The result was our tests took over 2 minutes to start up. So we decided to optimize things a bit. Here’s what we did:
1. Making sure our scripts were only loading the libraries they required at the moment they needed them.
All that tweaking reduced the test start up overhead to around 45 seconds which is still hardly acceptable. Are there other ways to speed up LoadFunctionLibrary?
The test itself is stored in Quality Center while the libraries are stored on the C drive. It seems that moving the test to the C drive drastically improves LoadFunctionLibrary’s performance. I then tried to move a subset of the libraries from the C drive to a Quality Center folder hoping that having the test and the libraries at the same place would speed things up. Unfortunately, it did not.
Marked as spam
Please log in to participate..