What operating system are you using? >> The issue occurs on all of the below OSs, Windows 2003 Server Windows 2000 Server RHEL 4U2(64 bit) RHEL 4U5(64 bit) RHEL 5(64 bit) SuSE Linux 9(32 bit) SLES10 SP1(32 bit) SLES 9SP3 ( 64 bit ) RHEL 4U2(32 bit) RHEL 4U5(32 bit) Solaris 9(64 bit) Solaris 10(64 bit) AIX 5.2 AIX 5.3(32 bit) HPUX 11i.v3(32 bit) And majorly on RHEL 5(64 bit), Solaris 9(64 bit), Solaris 10(64 bit)
<< What version of STAF are you using? >> 3.2.3 << What type of test are you running (just a high level overview)? >> Its a set of API tests for C,C++,Java all invoked using a batch file ( CShell , Windows Batch ) << How are you invoking it without STAF? >> I can simply execute the batch/ shell scripts. << How are you invoking it with STAF? >> I am using STAF Java APIs. A simple example is below:- handle.submit2(testMachine.getIp(), "PROCESS" ,"START COMMAND mytests.csh mytestsuite WORKDIR /myhome/mytestdir/ RETURNSTDOUT STDERRTOSTDOUT WAIT STDOUTAPPEND /myhome/mytestdir/log.out"); << I will update you with trace. Many thanks, Saneesh Joseph ________________________________ From: Charles Rankin [mailto:[EMAIL PROTECTED] Sent: Friday, February 15, 2008 8:46 PM To: Joseph, Saneesh Cc: staf-users@lists.sourceforge.net Subject: Re: [staf-users] Performance issue with STAF?? [EMAIL PROTECTED] wrote on 02/15/2008 06:26:31 AM: > I observed that STAF takes much more time - about 2.5 times - as > compared to the manual execution. > > I am running a batch file ( around 500 test cases ) using staf on a > remote machine that takes more than an hour, and 17-20 mins otherwise. > Is that because of a lower memory utilization by STAF? Is there any > option to increase the memory allocated to STAF so that I can bring down > the execution time? We'll need a good bit more detail to help find a root cause here. In general, STAF is designed for minimal overhead (when idle). So, if you've got a Perl script that you run from the command line on a system and it takes X amount of time to run (assuming STAF isn't even installed), then it should still take basically X amount of time to run if you have STAF execute the command for you. Any differences would almost certainly be due to environment differences (different user, different environment variables, etc.) Let's get some basic information and progress from there. What operating system are you using? What version of STAF are you using? What type of test are you running (just a high level overview)? How are you invoking it without STAF? How are you invoking it with STAF? It would also be useful to look at "top" (on Linux) or Task Manager (on Windows) to see if STAFProc is actually consuming significant CPU cycles or using large amounts of resident heap. If you see that it is, please post some stats/numbers for us. Finally, if it is consuming a lot of CPU, you will probably want to turn on tracing (see sections 4.11 and 8.18 in the STAF User's Guide) so that you can see what activity is occurring within STAF. It would probably be best to trace to a file so that you can post the trace as well. -- Charles Rankin ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ staf-users mailing list staf-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/staf-users
