Вы находитесь на странице: 1из 4



The statistics gathered above reflects the memory usage of the Siebel gateway
server. It shows excessive memory usage. From the figures it is obvious that the
current available memory is about 577MB (0.6 gb). This low memory has given
rise to a high paging activity.
The second diagram purely indicates a high disk usage for paging activities. The
Disk Queue Length is above average this is a proof of the paging statistics in the
first diagram (Pages/sec) , Page Faults/sec etc). from the statistics of the first
figure, we see that the system creates about two pages on the hard disk per
second. The creation of pages in the hard disk indicates a hard paging and the
effect of this is that the system during memory insufficiency develops page
faults. Page fault occurs when the system references a particular section of the
harddisk but that section either does not contain the needed data or it has not
been mapped. The Page fault per sec in this statistics states that there are about
2,938 per second. This is extremely dangerous for the operation of the system.
The performance of applications in general terms will suffer when there is
insufficient RAM and excessive hard page faults occur. It is imperative that hard
page faults are resolved in a timely fashion so that the process of resolving the
fault does not unnecessarily delay the programs execution.
We can also see that there are also cache faults recorded in the statistics drawn
from the (.236) server. The system file cache uses Virtual Memory Manager
functions to manage application file data. The system file cache maps open files
into a portion of the system virtual address range and uses the process working
set memory management mechanisms to keep the most active portions of
current files resident in physical memory. Cache faults are a type of page fault
that occur when a program references a section of an open file that is not
currently resident in physical memory. In the above statistics (Figure A), it is as
high as 2,128 faults per sec. Usually Cache faults occur due to insufficient
memory available to be used.


A comparison of the statistics above with that of the (.240) server is describe
here. This server is one of the Siebel application object manager servers. The
Statistics show that like the others it is under system resource insufficiency. The
memory available is about 5.5 gb. This is not as low as the available memory for
the .238 application server which is just a few megabytes.
On this server there are lesser page creations per second (2 pages ). The
memory cache faults developed on this server is about a half of that generated
on the (.236 and .238 ) server. The page faults is also about 2,328.
A combination of all the memory usage by the three servers. The statistics has
proven that the .238 server has a higher contention than the other servers. This
is the possible reason for the unusable state of the server during peak periods. To
push an even distribution of the application load, we could drop the server
(.238). This will make the 236 and 238 share the load.
The expected impact of this action is an even distribution of the load across the
available application servers.