POLL: Do your typical printers/MFPs have STANDARD or UPGRADED memory capacities?
Please comment. If you upgraded, why? Was it required by a certain feature? Did upgrading memory solve or improve any issues?
Upgraded because the KM iMFP software required the memory upgrade.
We upgraded our printer's memory when we found that it eliminated or reduced printing problems of pdfs and ppt slides that had high quality images/graphics embedded.
Were you able to take a particular problematic document and saw it resolved after the memory upgrade? Do you happen to remember what printer model it was and how much memory it had before and after the upgrade?
Basically Powerpoint files and PDFs with high-quality art work/graphics were our biggest problems. Usually those came from Art History classes, Nursing classes with high-quality images of anatomy, similar classes, etc. We use almost exclusively Xerox Phaser 5550 DT printers. They come stock with 256MB of memory and we upgraded them to 1GB. Once we did that upgrade, the types of files like what I mentioned no longer gave us problems.
We did the same thing with our Phaser 5550's but only up to 512.
FYI - We also noticed an issue with our Xerox MFD's, even though they had upgraded memory and hard drives. Users were complaining their jobs were taking too long to print and in some cases not printing. After investigating we found that the problem was the overwrite process. It was set to overwrite each job in real time. The MFD would overwrite the first job before printing the next one. In our high volume areas, all it would take to start backing things up was one or two large jobs. As more people sent jobs, the wait increased, causing "slow" printing, and some folks giving up on waiting for the job to print. Once we switched over to having the overwrite occur once daily at 2:00 AM, the problem went away.
Complex pages within documents, long multi-page jobs, or large spool files will require extended memory for optimum processing at the printer. When a printer receives a job over the network, it first buffers the inbound data to memory and then, if it has a hard disk, it spools overflow to the hard disk. If it does not have a hard disk, then the printer is forced to "chunk process" the job based on what is already in memory. To do this, it first has to tell the sending computer (the Pharos print server in this case) to stop sending data by issuing a "TCP Zero Window" packet. It will continue to deny data receipt until it can free up internal memory by spitting out sheets. Some job options may actually prohibit this behavior, causing the printer to reject the job after receiving and processing (as best it can) the data it already has.
If the printer does have a hard disk, it will offload the remainder of the inbound data to the hard disk for temporary storage. Then it will again begin to "chunk process" the job based on available physical memory and any "virtual memory" available within the swap space of its hard disk. Thankfully, since the entire job has been received and stored on disk, this usually results in a completed print out.
Retrieving data ...