The following question was sent to the staf-users mailing list by Shuki 
Zaitman but was bounced for some reason.

During STAF investigate there is some issue that unknown & I don?t see any 
mention in the documents
 
1.      Performance issue. As I saw, STAF processes don?t have any 
performance issue. Does right?
2.      Stability issue. The plan is that STAF will be running for two 
weeks. Does any one have experiment with that? What about memory usage & 
etc.

Answer:

There aren't any known performance issues with STAF processes.

The STAFProc daemon is intended to run for any length of time.  We have 
run STAFProc for months on many machines. 

See section "1.10 What is the performance overhead of running STAF?" in 
the STAF FAQ at http://staf.sourceforge.net/current/STAFFAQ.htm#d0e265 for 
more information about the memory usage, etc.

As a general rule, STAF takes up very little system resources. STAF's 
in-memory size (without any additional external services) is about 2.5-5 
MB (depending on the platform). On an idle STAF system (i.e., one in which 
there are no requests currently being handled by STAF) STAF consumes 0% 
CPU on a Windows system and a VERY limited amount on unix systems. On 
unix, we have a thread which wakes up once a second to see if any STAF 
processes have completed. STAF was designed to consume as little system 
resources as possible, as we know that people want their test systems as 
close to clean-room conditions as possible. 


--------------------------------------------------------------
Sharon Lucas
IBM Austin,   [EMAIL PROTECTED]
(512) 838-8347 or Tieline 678-8347
-------------------------------------------------------------------------
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

Reply via email to