Forum Discussion

Ptaun's avatar
Ptaun
Occasional Contributor
9 years ago

Large Number of Files in TestComplete Causing Memory Issue

For various internal reasons, we are moving from an external keyword driven framework to writing our test scripts in JScript within TestComplete itself.  To test the scalability and the eventual perf...
Ptaun's avatar
Ptaun
Occasional Contributor
9 years ago
Just once.
Marsha_R's avatar
Marsha_R
Icon for Champion Level 3 rankChampion Level 3
9 years ago

How long does it take if you take the USEUNIT out? 

  • joseph_michaud's avatar
    joseph_michaud
    Icon for Staff rankStaff
    9 years ago

    I think this is going to depend on the size of your 250 files.  When TestComplete runs a test, it processes all the script files.  I can imagine that if you have lots of very large script files, it will take a while to process.  How large are your files?  Can you provide a sample?

     

    Try sprinkling some Log.Message() calls at the top level in your script files just to see how long it takes to process the files.

    • Marsha_R's avatar
      Marsha_R
      Icon for Champion Level 3 rankChampion Level 3
      9 years ago

      joseph_michaud  That's what I was trying to get at with removing the USEUNIT.  If the empty function runs really fast then, we know the 250 is the culprit.

      • Ptaun's avatar
        Ptaun
        Occasional Contributor
        9 years ago

        Here is what I have found:

         

        • 35 to 40 seconds with the 250 as is
        • 28 seconds without the functions in the 250, just the USEUNITs
        • 17 seconds without anything in the 250, just empty files

         

        From there, an assumption can be made regarding how much overhead the USEUNITs generate.  I have also found that using require instead of USEUNIT does not reduce that time any.