Java Virtual Machine Storage
Free Storage Available
This is the amount of remaining storage available in bytes to the JAVA virtual machine (JVM) and therefore the PServer application.
Maximum Storage Available
This is the total amount of storage available in bytes to the JAVA virtual machine to run PServer application.
F/T percent
This is the percent of remaining JVM Free Storage for available use by PServer. The ratio of Free to Total Storage.
Change
This will show the change in virtual storage consumption over that last interval,
A positive number denotes an increase in virtual storage consumption.
A negative number means a decrease and giveback of storage via "garbage collection".
Task Information
Active Task Count HighWater Marks
These counters will display the greatest number of dispatched worker tasks used since the proxyserver has been started (or resumed) for each protocol service. If the number is approaching the maximimum value listed below then you may want to increase the current maximum.
Count of total Open Subtasks
These counters will display the current number of dispatched worker tasks plus helper subtasks currently open. During idle periods this number should be no greater than the minimum value listed below.
Performance Value Settings
Maximum number of Tasks/Protocol
The number of tasks or thread programs that are permitted to be created to service Internet traffic. The greater the number of threads, the smaller the probability of experiencing a queueing effect on requests and responses travelling between the Internet and your computers. But the more threads you have the more real storage and CPU cycles are consumed. Larger machines can accomodate a greater number of tasks.
Minumum number of Tasks/Protocol
The number of tasks or thread programs that are required to be available for request/response processing. You may want to leave at some that remain "HOT" and ready to process incoming requests immediately. There is a greater expense associated with starting and stopping tasks. Leaving some HOT will eliminate the overhead of starting those tasks.
(Note: The difference between the Minimum and Maximum values is the permitted Expansion/Contraction value. The number of tasks servicing this particular protocol will be allowed to grow to a maximum, then shrink back. The expansion factor and expansion rate is a function of the request load being placed upon the proxy server at any given time. Currently each protocol has its own set of tasks, however they share the Max and Min values.)
IDLE Task Timeout Value
This is the number of seconds that a task must remain IDLE prior to the supervisor allowing the task to "evaporate" and release its storage. Short TIMEOUTS of less than one minute may be unproductive insofar as overhead reduction. We recommend that your TIMEOUT values are 60 seconds or more.
I/O Task Timeout Value
This is the number of seconds that a task may wait for more input from either the client or server before the supervisor will make a decision to end the task and reclaim its storage. Short TIMEOUTS of less than one minute may be unproductive insofar as overhead reduction. We recommend that your I/O TIMEOUT values are 60 seconds or more.
+---------+ +----------+ +----------+
| | input | | output | |
| | ---------------> | Proxy | ----------------> | Internet |
| Client | output | Server | input | website |
| | <--------------- | | <---------------- | |
| | | | | |
+---------+ +----------+ +----------+
I/O Task Timeout Value
This is the number of client requests that may remaing pending in each of the protocol servers before requests are discarded and the client is signalled that the server is too busy to accomodate the request. Keep in mind that large backlogs values can result in excessive queue lengths (ie. a long checkout line). High backlog values should be met with high maximum tasks values. These tasks evaporate upon completing their service. We recommend that your request BACKLOG values be at least 16.
Internet Inbound I/O Buffer Size
This is the buffer size, in bytes, used to accomodate traffic incoming from the Internet into the proxy server.
Internet Outbound I/O Buffer Size
This is the buffer size, in bytes, used to accomodate traffic outgoing to the Internet from the proxy server. Generally much less than the inbound Internet traffic.
Intranet Inbound I/O Buffer Size
This is the buffer size, in bytes, to accomodate traffic coming off of the proxy server destined for a client computer on your LAN.
Intranet Outbound I/O Buffer Size
This is the buffer size, in bytes, to accomodate traffic going out from the client computer to the proxy server destined for an Internet site. Generally, this is much less than the inbound intranet traffic.
[Return to User Guide Table of Contents]
[Return to Index]
[Return to Cullen Programming Home Page]
Copyright © Cullen Programming 1999, 2008