For Release 3.x spool servers, all output requests and related management activities are anchored by a single spool work process. Needless to say, processing bottlenecks can be a common occurrence, forcing administrators to add additional R/3 servers just to get more spool work processes. Release 4.x spool servers, which can support multiple spool work processes, yield far better throughput and performance. Just how many spool work processes should you set up on your Release 4.x spool server? This article provides you with evaluation criteria and guidelines to answer that question and simple scenarios that illustrate how to apply these factors in a real-world situation.