G
Guest
We have an application that prints a combination of text and vector graphics
using the GDI+ support in DotNet.
Everything is fine when we print to printers on the same LAN as the
application, but printing over the WAN to a remote printer is slow. I ran
some benchmarks for three cases:
· Transfering a file: 900,000 bits/sec
· Printing from our DotNet application: 225,000 bits/second = 7.5 pages/minute
· Printing an RTF file with similar content from WordPad: 560,000
bits/second = 17 pages/minute
These are based on the spool file sizes as reported in the Control Panel
printer window for the printer. These sizes are about 220KB per page in both
cases.
Also it seems that, when printing from WordPad, the spool files are of RAW
type while, presumably, when printing from DotNet they are of type EMF.
Why is printing from DotNet so slow? What do we need to do to improve the
speed by the factor of about four that seems to be potentially available?
using the GDI+ support in DotNet.
Everything is fine when we print to printers on the same LAN as the
application, but printing over the WAN to a remote printer is slow. I ran
some benchmarks for three cases:
· Transfering a file: 900,000 bits/sec
· Printing from our DotNet application: 225,000 bits/second = 7.5 pages/minute
· Printing an RTF file with similar content from WordPad: 560,000
bits/second = 17 pages/minute
These are based on the spool file sizes as reported in the Control Panel
printer window for the printer. These sizes are about 220KB per page in both
cases.
Also it seems that, when printing from WordPad, the spool files are of RAW
type while, presumably, when printing from DotNet they are of type EMF.
Why is printing from DotNet so slow? What do we need to do to improve the
speed by the factor of about four that seems to be potentially available?