Those doing planning might well be interested in these stats from a real-world ThinPrint deployment in respect of how well it compresses jobs.

We started by testing a job typical of the users; a PDF consisting of scanned black and white pages. He we measured the data passed on the network for each of ThinPrint’s compression settings.

SettingJob size (%)Quality
None 100 Original
Optimal 90 Near perfect
Maximum 58 Good; useable
Extreme 19 Medium; readable
No images Not tested

Pretty decent, we thought, for a test document that is all A4 images. Now to try a pilot.

One all VDI office has 63 users. All of them use Wyse terminals, so using the ThinPrint compression built in to VMware View is not an option. We wanted to test whether or not ThinPrint was worth buying. Of the 63, 40 use only ThinPrint printers. For them, their print jobs go from VM to the .print Engine for VMware View in the datacentre, to the Windows print server in the office. The others print direct from their VDI desktop hosted in the datacenter to the Windows print server in the office.

There are four printers, three HP A4 monochrome lasers and one Xerox A3 colour printer (with the colour drums removed…). Each printer is accessible via ThinPrint and directly. ThinPrint is set to ‘Optimum’ compression.

I dragged out the stats on the amount of print data transferred for each of six consecutive business days:

DayThinPrint data (b)Uncompressed data (b)
1 26340958 234708630
2 67133657 121979299
3 113838547 189902846
4 46067764 145088982
5 42741516 155059692
6 55769733 172241368

--> the rest is on the blog :

http://www.yellow-bricks.com/2010/02/09/should-i-buy-thinprint-real-world-numbers/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+YellowBricks+%28Yellow+Bricks%29