Closed Bug 11957 Opened 25 years ago Closed 25 years ago

[PP] Win32 - Print jobs 14 times larger than Communicator

Categories

(Core :: Printing: Output, defect, P3)

x86
Windows NT
defect

Tracking

()

VERIFIED INVALID

People

(Reporter: cpratt, Assigned: dcone)

References

()

Details

(Whiteboard: [Perf])

Build ID: 1999070614 (August 15, 1999 M9 build)
Platform: Windows NT

To reproduce (Netscape internal instructions):
- From the Start menu, select Run; type '\\flotsam\mackeral'
- Load http://www.yahoo.com in Communicator 4.7 and Apprunner
- Print the page from both 4.7 and Apprunner
- Look at the 'mackeral on FLOTSAM' window

Result: Here are the sizes of the respective print jobs:

Apprunner - 1.99 M bytes
Communicator 4.7 - 147 K bytes

Expected result: Presumably, we want to keep the size of print jobs as small as
possible to reduce network congestion and spooling/printing time.

Marking [PP] as the print job size on the Mac is 28 K (Apprunner), 40 K (4.7);
that's the kind of performance we should be seeing in Seamonkey (I expect).
Whiteboard: [Perf]
Putting on [Perf] radar.
Status: NEW → ASSIGNED
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → INVALID
1.) The size of the print job was 114 k when I tested.
2.) Control of the print job size is not something we can control, without
extensive overhaul of the entire layout system since printing is just layout of
the document to the printer.  The job size is directly related to the number of
windows GDI calls and image bits sent to the printer from the Layout system.
If we can't control it, that's fine. Marking verified invalid.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.