There are two things to determine:

How your machine is doing
What does the DM use
What the impact of FV will be

You should use 'vmstat' (ignoring the first line of data; it's garbage) on
your machine as is. The free memory column tells you how much RAM you are
using now. The paging columns tell you if the machine is using the disk as
virtual memory (this is not a good thing since RAM is cheap and virtual
memory eats CPU cycles).

For example, this output from vmstat tell me that my machine has 45MB free.

1AW51C# vmstat 5 30
 procs     memory            page            disk          faults      cpu
 r b w   swap  free  re  mf pi po fr de sr m0 m1 m2 m3   in   sy   cs us sy
id
 0 0 0 268072 61996   0  11  3  0  0  0  0  0  0  0  0   31  484  301  0  1
99 # Ignore this one
 0 0 0 257204 45004   0   3  0  0  0  0  0  0  0  0  0   36  529  319  0  1
99 

The ps command reports that the DM requries about 3MB for the first instance
and probably less for more. (I didn't check). The DM could be either dm_wp50
or default_dm on your system. Use the following to see which DM is your
default DM:

sum /usr/fox/wp/bin/dm_wp50 /opt/fox/wp/bin/default_dm
/opt/fox/wp/FoxView/foxview

At this point, we know what you have free and what the DM needs. Now, for
FoxView.


According to the ps command, FoxView (default_dm on my 51c) requires 11.723
MB of RAM.

ps -el | head ; echo ... ; ps -el | grep default_
 F S   UID   PID  PPID  C PRI NI     ADDR     SZ    WCHAN TTY      TIME CMD
19 T     0     0     0  0   0 SY f0271b28      0          ?        0:00
sched
 8 S     0     1     0  0  41 20 f5bab678    106 f5bab848 ?        0:00 init
19 S     0     2     0  0   0 SY f5bb29a0      0 f0288f48 ?        0:00
pageout
19 S     0     3     0  0   0 SY f5bb2340      0 f028d1bc ?        0:23
fsflush
 8 S     0  1778     1  0  41 20 f5bb1ce0    340 f5baa814 ?        0:00 sac
 8 S     0  1779     1  0  61 20 f5bb1680    355 f591f3d6 ?        0:00
ttymon
 8 S     0   982   975  0  55 20 f5bb1020    354 f611ee0e ?        0:00
lpNet
 8 S     0   914     1  0  77 20 f5fa3988    418 f591f21e ?        0:00
statd
 8 S     0   894     1  0  41 20 f5d0e660    461 f591f35e ?        0:00
rpcbind
...
 8 S     0  1532  1091  0  50 20 f63cf020  11723 f633c8c6 ?        0:05
default_

The program top reports 12 MBytes.

However, this memory includes both the data portion of the program and the
code portion. The code is shared.

So, I ran vmstat(1) at 5 second intervals for 30 iterations with one
FoxView, then 2, then back to one.

As you can see, the second instance required about 6MB of new RAM. The
stated requirement is 8MB of RAM per FV instance.


1AW51C# vmstat 5 30
 procs     memory            page            disk          faults      cpu
 r b w   swap  free  re  mf pi po fr de sr m0 m1 m2 m3   in   sy   cs us sy
id
 0 0 0 268072 61996   0  11  3  0  0  0  0  0  0  0  0   31  484  301  0  1
99 # Ignore this one
 0 0 0 257204 45004   0   3  0  0  0  0  0  0  0  0  0   36  529  319  0  1
99 # Single instance
 0 0 0 257204 45004   0   0  0  0  0  0  0  2  0  1  0   93  618  347  2  2
96
 0 0 0 257204 45004   0   0  0  0  0  0  0  0  0  0  0   35  527  313  0  1
99
 0 0 0 252392 42036   0 300  0  0  0  0  0  0  0  0  0   95 3080  546 55 24
21
 0 0 0 249268 39288   0  18  0  0  0  0  0  0  0  0  0   60 2008  432 13  4
83 # Second started
 0 0 0 249108 39244   0   0  0  0  0  0  0  0  0  0  0   48  696  344  0  0
100
 0 0 0 249108 39244   0   0  0  0  0  0  0  0  0  0  0   50  689  341  0  0
100
 0 0 0 249108 39244   0   1  0  0  0  0  0  0  0  0  0   74  789  383  0  0
99

 0 0 0 249108 39244   0   0  0  0  0  0  0  2  0  0  0   91  749  356  1  1
98
 0 0 0 249108 39244   0   0  0  0  0  0  0  0  0  0  0   50  696  344  0  0
100
 0 0 0 249100 39240   0   0  0  0  0  0  0  0  0  0  0   48  698  343  0  0
100
 0 0 0 249100 39240   0   0  0  0  0  0  0  0  0  0  0   54  693  344  0  1
99
 0 0 0 249096 39236   0   1  0  0  0  0  0  0  0  0  0   55  742  370  1  0
99
 0 0 0 253916 42620   0   0  0  0  0  0  0  0  0  0  0   38  563  319  1  2
97 # Second stopped
 0 0 0 257132 44884   0   0  0  0  0  0  0  0  0  0  0   25  497  302  0  0
100
 0 0 0 257132 44884   0   0  0  0  0  0  0  0  0  0  0   25  488  300  0  0
100
 0 0 0 257132 44884   0   0  0  0  0  0  0  0  0  0  0   27  525  303  0  1
99
 0 0 0 257132 44884   0   0  0  0  0  0  0  0  0  0  0   47  534  331  0  0
99

Now, you know what capacity your machine has and what FV will demand and can
do the arithmetic.

Note, the id column can be used to view the impact on CPU time of mulitple
FVs and of FV vs. DM.

One last item, FV requires a lot of disk space in /opt. So check your /opt
partition for free space:

df -F ufs -k


Regards,


Alex Johnson
10707 Haddington
Houston, TX 77043
713.722.2859 (office)
713.722.2700 (switchboard)
713.932.0222 (fax)
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> 


        -----Original Message-----
        From:   [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]]
        Sent:   Thursday, April 26, 2001 9:08 AM
        To:     [EMAIL PROTECTED]
        Subject:        Minimun RAM for FoxView

        We are to change our IA system (AW51B with 4.3 software) from DM to
FoxView (and 6.2.1 software). 

        We have only 32 Mb in some of our WP and 64 Mb in our AW. 

        What's the experience of the Users about the "real" minimun RAM
required (and disk space) to work with two FoxViews per station? Foxboro, in
the installation Notes of this version, ask for only 32 Mb but we think that
is not a "real" number...

        Thank you in advance and best regards. 

        Pedro Hernandez 
        Process Control Manager 
        REPSOL-YPF Quimica 
        Puertollano (C.Real) 
        SPAIN 
        

-----------------------------------------------------------------------
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]

Reply via email to