Examples:
Extremely large Installation
• 600 Transactions per hour
• All sizing numbers are based on Request per Second (RpS).
• 1RpS equals about 20 transactions per hour.
• 600/20 = 30 Requests per Second
wwService/ww.dll servers:
• 2 Servers (1 Server for pages support and 1 for P@H tickets)
• 16 CPU cores
• 64 worker processes
• 64 GBytes of RAM per server.
Important: Total resources must be split equally between both servers.
E-Commerce pages server:
1 Server (could be divided into 2 servers in a load balanced environment)
System Totals:
• 16 CPU cores
• 32 worker processes
• 64 GBytes of RAM.
Very Large Installation
• 300 transactions per hour
• This works out to 300/20 = 15 requests per second.
wwService/ww.dll Servers:
• 2 Servers (1 Server for pages support and) 1 for P@H tickets.
• 8 CPU cores
• With 32 worker processes
• 32 GBytes of RAM per server
Important: Total resources must be split equally between both servers.
E-Commerce pages server:
• 1 Server
• 8 CPU cores
• 16 worker processes
• 32 GBytes of RAM
Large Installation
• 160 transaction per hour design load
• 8 requests per second
wwService/ww.dll Servers:
• 2 Servers (1 Server for pages support and 1 for P@H tickets)
• 4 CPU cores
• With 16 worker processes
• 16 GBytes of RAM per server
Important: Total resources must be split equally between both servers.
E-Commerce pages server:
• 1 Server
• 4 CPU cores
• 8 worker processes
• 16 GB of RAM
Medium Installation
• 80 transaction per hour design load
• 4 requests per second
wwService/ww.dll Servers:
• 1 Server
• 4 CPU cores
• With 16 worker processes
• 16 GBytes of RAM per server
E-Commerce pages server:
• 1 Server
• 2 CPU cores
• 4 worker processes
• 8 GBytes of RAM
Small Installation
• 20 transaction per hour design load
• 1 request per second
wwService/ww.dll Servers:
• 1 Server
• 2 CPU cores
• With 4 worker processes
• 4 GBytes of RAM per server
E-Commerce pages server:
• 1 Server
• 2 CPU cores
• 2 worker processes
• 4 GBytes of RAM