From: Sharon L. <lu...@us...> - 2008-01-30 18:48:35
|
The following question was sent to the staf-users mailing list by Shuki=20 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 =20 1. Performance issue. As I saw, STAF processes don?t have any=20 performance issue. Does right? 2. Stability issue. The plan is that STAF will be running for two=20 weeks. Does any one have experiment with that? What about memory usage &=20 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=20 run STAFProc for months on many machines.=20 See section "1.10 What is the performance overhead of running STAF?" in=20 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=20 in-memory size (without any additional external services) is about 2.5-5=20 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%=20 CPU on a Windows system and a VERY limited amount on unix systems. On=20 unix, we have a thread which wakes up once a second to see if any STAF=20 processes have completed. STAF was designed to consume as little system=20 resources as possible, as we know that people want their test systems as=20 close to clean-room conditions as possible.=20 -------------------------------------------------------------- Sharon Lucas IBM Austin, lu...@us... (512) 838-8347 or Tieline 678-8347 |