Bookshelf Home | Contents | Index | PDF |
Siebel Deployment Planning Guide > Application-Level Deployment Planning > Siebel Product Configurator Deployment Planning > Example of Sizing the Cache with SnapShot ModeThis topic provides an example of sizing the Siebel Product Configurator cache with SnapShot mode. This topic is part of Siebel Product Configurator Deployment Planning. AssumptionsThe requirement is to support 5000 concurrent Siebel Call Center users. Among them, at any time, 100 users use Siebel Product Configurator. This means:
SizingBecause all of the caching and services are specific to the Application Object Manager process on a Siebel Server, first you must estimate the size of the Call Center deployment. (The following numbers are used for example only, and are not indicative of Call Center sizing.)
To support cached objects, factories, and workers for all 100 users, the following conclusions can be drawn:
In the preceding example, the cache size in this case for each Application Object Manager equals the size of the factory cache plus the size of the worker cache. Expressed as a formula, it looks like this: 5 plus 25 equals 30 MB for each Application Object Manager. Therefore, the Siebel Product Configurator cache requires a total of 30 times 25, which equals 750 MB for each server. The server parameters would be set as follows for each Siebel Server (Application Object Manager): Observations About SizingFrom the preceding sizing exercise, it is clear that the Siebel Product Configurator cache must be actively managed for best performance using appropriate resources. It is extremely important to go through the exercise of sizing the cache. In some cases, the cache requirements might be such that they require additional application servers to fully support all of the users with good response times for load time. In addition to the preceding calculation, in some situations it is appropriate to set the number of workers according to how much memory is available once enough memory has been allocated to the factory cache and application overhead. The details of this calculation are specific to an individual implementation's average factory size, average worker size, and average Application Object Manager process size. The average Application Object Manager process size depends on the number of Application Object Manager processes, the total memory available, and the maximum process size for the operating system being used. For additional assistance in this area, contact your Oracle sales representative for Oracle Advanced Customer Services to request assistance from Oracle's Application Expert Services. |
Siebel Deployment Planning Guide | Copyright © 2017, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |