Document Type (Doc. Size)
Explanation of Bandwidth Performance ResultsThe differences in rendering size on the server compared to the resulting client-side size underscore the need to plan for sufficient disk space for the Spooler folder on the Terminal Server. By default, this location exists in the following path: %SYSTEMROOT%\System32\spool\PRINTERS This path resides on the same partition as the OS. If the OS is on a small partition, this can affect redirected printing, especially if disk space is exhausted under heavy load. You can move the Spooler folder location to another folder, or to a partition on another drive set. To change the location, open the Printers folder on the Terminal Server, choose File, Server Properties, and then choose the Advanced tab. This global setting applies to all queues on the server, including redirected queues. Job sizes written to the Spooler folder on the server side are based primarily on the contents of the job. As the results show, large and complex PDF and Word documents that contain a great deal of text formatting and many bitmap images can swell the job to a size many times larger than the original file size. The results emphasize that if you pause the server-side print queue and spool a print job, the job can appear very large when compared to other versions of the OS or when spooling the same job or document on the client side. This is because the spooled job on the server is written to disk in enhanced metafile (EMF) format and has not finished rendering to RAW (ready to print) format for transmission across the Virtual Channel down to the client. Note: Do not use paused job sizes on the server side as a measure of how much data will be transmitted over the wire for a given print job. This measurement is not accurate, as demonstrated by the rendered size at the client. The conversion of the spool files to RAW format requires additional memory and CPU resources. Most of the CPU load during these tests was seen within the printing applications themselves, with a negligible bump in Spooler usage. For more information about CPU loads, see Scalability Performance Results. The results demonstrate that wire speed is a big part of the equation in terms of output speed on the client-side printer. In low-bandwith situations, further optimizations of output speed may be obtained by reducing client-side session screen depth, as well as eliminating any other unnecessary wire traffic over the slow link between client and server. Katalog: windows -> shared -> community -> docs windows -> Benefits of Microsoft Windows x64 Editions docs -> Windows 2000 Chkdsk Management windows -> Windows 2000 Accessibility Features Download 486,5 Kb.
|