Quote:
Originally Posted by DaiNasty
That's an interesting though. Presumably an image of the print job has to be built up somewhere before printing can begin. Where does that happen?
Is it in the printer's memory, the printer server or the spooler process in the server?
I'd like to understand how it works, and that could have a bearing on why it hits on the system so hard.
|
On disk and in memory on the client pc via the client spooler service to the print server's memory which will in turn perform a similar process to the client pc and stream the job via it's own memory and spooler service to the printer's memory buffer.
When the spooling job becomes larger than the print server's memory may well be where the problems start to occur and as Rob mentions above the OP would probably be best served depolying a server based print server with a suitable amount of memory. Whatever the OP's print server is doing to deal with an amount of data it can't buffer may be having unpredictable consequences on the LAN.
Also, when the job is translated into something the printer can understand (PCL, PostScript etc) the actual raw amount of data sent to the printer can be very large indeed, much larger than the actual size of the file on disk storage.