Performance Tuning Guide > Tuning Siebel Communications Server for Performance >
Topology Considerations for Siebel Email Response
Processing inbound email messages makes more demands on server resources, particularly CPU usage levels, than processing outbound messages.
Processing of inbound messages associated with a single response group must be handled on a single machine.
If inbound message volume warrants it and if multiple server machines are available to run CommInboundRcvr, CommInboundProcessor, and other components, then you should consider running CommInboundRcvr and CommInboundProcessor on separate machines (or machines) from other Communications Server components. Topology options for these component are different for real-time and nonreal-time processing.
For more information about CommInboundRcvr and CommInboundProcessor, see Siebel Communications Server Administration Guide and Siebel Email Response Administration Guide.
CommOutboundMgr and Siebel Smart Answer (Smart Answer Manager) may be run together on a different machine (or machines), as appropriate.
Combining processing of messages for multiple email accounts in a single response group can make processing of inbound messages more efficient. However, if message volume is expected to grow, then limiting the number of email accounts processed by each response group will give you more flexibility to distribute processing across multiple servers, and thereby avoid processing bottlenecks.