Chapter 2   Sizing Your System


This chapter discusses how to use a sizing calculator to estimate the initial hardware requirements for your iPlanet Market Maker system.

This chapter contains the following sections:

• Overview of the Sizing Calculator

• Example 1: Auction-Intensive Marketplace

• Example 2: RFx-Intensive Marketplace

• Example 3: Exchange Intensive Marketplace

Overview of the Sizing Calculator

---

Based on the performance tests conducted using the development setup, you can develop a sizing calculator to derive an initial estimate of the size of the hardware configuration needed to meet the requirements of the marketmaker organization.

---

Note	The calculator as discussed in this chapter is intended to be a rough guide. Additional parameters should be considered when estimating hardware requirements.

---

Table 2-1 represents a typical sizing calculator.

Table 2-1    Sizing Calculator

					Estimated Number of CPUs
Module	Enter the Number of Concurrent Users Below	Response Time (Seconds)	Number of Pages Served Per Hour	iWS	iAS	LDAP	Oracle	iMQ
Community Registration
Catalog Searching
RFx Requests/Responses
Auction Bidding
Order Management Sys (OMS))
Exchange
Sub Total
Total Number of CPUs Required With Safety Factor 1.5

In the second column (Enter the Number of Concurrent Users Below) of the sizing calculator, enter the number of users that you expect to be actively and simultaneously performing each of the commonly used functions, as listed in the first column.

After entering the numbers, click Calculate to display the following results:

• Response Time—The number of seconds it takes for the software to respond to user requests submitted in each module.

• Number of Pages Served per Hour—The maximum number of actual pages served in an hour when the specified function is performed by the given number of users.

• CPUs for iPlanet WebServer—The following hardware requirements for the web server:
  • The number of CPUs required for the iPlanet WebServer for each functional module.

  • The total number of CPUs required for the iPlanet WebServer for all modules.

  • The total number of CPUs required for the iPlanet WebServer for all modules, considering a reasonable load factor.

• CPUs for iPlanet Application Server—This column provides the following hardware requirements for the application server:
  • The number of CPUs required for the iPlanet Application Server for each functional module.

  • The total number of CPUs required for the iPlanet Application Server for all modules

  • The total number of CPUs required for the iPlanet Application Server for all modules, considering a reasonable load factor.

• CPUs for iPlanet Directory Server—This column provides the following hardware requirements for the LDAP database:
  • The number of CPUs required for the LDAP database for each functional module.

  • The total number of CPUs required for the LDAP database for all modules.

  • The total number of CPUs required for the LDAP database for all modules, considering a reasonable load factor.

• CPUs for Oracle—This column provides the following hardware requirements for the Oracle database:
  • The number of CPUs required for the Oracle database for each functional module.

  • The total number of CPUs required for the Oracle database for all modules.

  • The total number of CPUs required for the Oracle database for all modules, considering a reasonable load factor.

• CPUs for iPlanet Messaging Queue—This column provides the following hardware requirements to run iPlanet Messaging Queue:
  • The number of CPUs required to run the iPlanet Messaging Queue for the Exchange module.

  • The total number of CPUs required to run the iPlanet Messaging Queue for the Exchange module.

  • The total number of CPUs required to run the iPlanet Messaging Queue for the Exchange module, considering a reasonable load factor.

From the Total with Load Factor (x 1.5) values in the table, you can derive an initial estimate of hardware requirements for the iPlanet WebServer, the iPlanet Directory Server, and the Oracle database.

Example 1: Auction-Intensive Marketplace

---

Table 2-2 represents the deployment of the iPlanet Market Maker software by a marketmaker firm that plans to use the marketplace primarily for hosting auctions. If you enter the numbers shown below in the second column (Enter the Number of Concurrent Users Below) and click Calculate, you see the numbers shown in the table.

Table 2-2    Sizing Calculator Results for Example 1

					Estimated Number of CPUs
Module	Enter the Number of Concurrent Users Below	Response Time (Seconds)	Number of Pages Served Per Hour	iWS	iAS	LDAP	Oracle	iMQ
Community Registration	10	3.983	3394.9	0.0064	0.2136	0.0480	0.1920
Catalog Searching	50	4.096	18365	0.134	1.8660	0.12	1.8800
RFx Requests/Responses	0	2.413	0	0	0	0	0
Auction Bidding	100	1.933	29957	0.44	2.32	0.2133	2.1867
Order Management Sys (OMS))	40	4.518	11010	0.04	0.8800	0.4640	0.944
Exchange	0	1.235	0	0	0	0	0	0
Sub Total	200		62726.9	0.6204	5.2796	0.8453	5.2027	0
Total Number of CPUs Required With Safety Factor 1.5				0.9966	8.0394	0.6020	7.64805	0

From Example 1, you can estimate the hardware requirements as follows:

• iPlanet WebServer (iWS) = 1 CPU

• iPlanet Application Server (iAS) = 8 CPUs

• iPlanet Directory Server (LDAP) = 1 CPU

• Oracle = 8 CPUs

Example 2: RFx-Intensive Marketplace

---

Table 2-3 represents the deployment of the iPlanet Market Maker software by a marketmaker firm that plans to use the marketplace primarily for procurement (RFx). If you enter the numbers shown below in the second (Enter the Number of Concurrent Users Below) column and click Calculate on the calculator, you see the numbers shown in the table.

Table 2-3    Sizing Calculator Results for Example 2

					Estimated Number of CPUs
Module	Enter the Number of Concurrent Users Below	Response Time (Seconds)	Number of Pages Served Per Hour	iWS	iAS	LDAP	Oracle	iMQ
Community Registration	10	3.983	3394.9	0.0064	0.2136	0.0480	0.1920
Catalog Searching	50	4.096	18365	0.134	1.8660	0.12	1.8800
RFx Requests/Responses	100	2.413	22407	0.1128	5.4872	1.28	7.5200
Auction Bidding	0	1.933	0	0	0	0	0
Order Management Sys (OMS))	40	4.518	11010	0.04	0.8800	0.4640	0.944
Exchange	0	1.235	0	0	0	0	0	0
Sub Total	200		55176.9	0.2932	8.4468	1.912	10.5360	0
Total Number of CPUs Required With Safety Factor 1.5				0.5058	12.7902	2.202	15.648	0

From Example 2, you can estimate the hardware requirements as follows:

• iPlanet WebServer (iWS) = 1 CPU

• iPlanet Application Server (iAS) = 13 CPUs

• iPlanet Directory Server (LDAP) = 3 CPU

• Oracle = 16 CPUs

Comparing Example 2 with Example 1, you can see that the total number of simultaneous users is the same. However, because the RFx module requires more processing power than the Auctions module, the number of CPUs required in Example 2 is greater.

Example 3: Exchange Intensive Marketplace

---

Table 2-4 represents the deployment of the iPlanet Market Maker software by a marketmaker firm that plans to use the marketplace primarily for hosting exchanges. If you enter the numbers shown below in the second (Enter the Number of Concurrent Users Below) column and click Calculate on the calculator, you see the numbers shown in the table.

Table 2-4    Sizing Calculator Results for Example 3

					Estimated Number of CPUs
Module	Enter the Number of Concurrent Users Below	Response Time (Seconds)	Number of Pages Served Per Hour	iWS	iAS	LDAP	Oracle	iMQ
Community Registration	10	3.983	3394.9	0.0064	0.2136	0.0480	0.1920
Catalog Searching	50	4.096	18365	0.134	1.8660	0.12	1.8800
RFx Requests/Responses	0	2.413	0	0	0	0	0
Auction Bidding	0	1.933	0	0	0	0	0
Order Management Sys (OMS))	40	4.518	11010	0.04	0.8800	0.4640	0.944
Exchange	100	1.235	30573	0.052	3.948	0.0864	1.28	2.08
Sub Total	200		63342.9	0.2324	6.9076	0.7184	4.296	2.08
Total Number of CPUs Required With Safety Factor 1.5				0.3366	4.5594	0.282	4.368	3.12

From Example 3, you can estimate the hardware requirements as follows:

• iPlanet WebServer (iWS) = 1 CPU

• iPlanet Application Server (iAS) = 5 CPUs

• iPlanet Directory Server (LDAP) = 1 CPU

• Oracle = 5 CPUs

• iPlanet Messaging Queue = 3 CPUs

Comparing this example with Examples 1 and 2, you can see that the total number of simultaneous users is the same. However, because the RFx and Auctions modules each require more processing power than the Exchange module, the number of CPUs required in Example 1 and in Example 2 is greater.