Vijay Chauhan

Hi guys,

I am developing XPSDrv. And during our performance measure tests, we have observed that,-

1. As compared to PS3 / PCL6 drivers, printing from XPSDrv is real slow. I mean forget filter processing, rendering time taken itself seems to be a lot more than my PS3 etc. drivers. Has anybody observed this

2. My 700KB MS word file, with some graphics and text in it, comes as 77MB output file. Note that this is the direct output from MXDWDRV.DLL and is not filter processed output. Where as my regular PS3 driver is just 20MB in size, way better.

Before this performance measurements, i was under impression that XPSDrv is going to be super cool with above aspects.. But now it has turned out the other way! Is this a technology advancement for the end user Or MS has plans to improve on MXDWDRV.DLL on above

Would love to hear on this from MSFT guys.

-Vijay



Re: XML Paper Specification (XPS) XPSDrv Printer driver - Is it very slow?

AnishM

Vijay,

Thanks for your input. Of course, MSFT is working on improving XPSDrv.

I appreciate you taking efforts in working with XPSDrv and reporting the issues you are facing.

1. Could you please share the statistics you have seen so far Also could you please the send the set of test documents to xpsinfo@microsoft.com with the same title as this message.

2. Your second case of 700KB MS word document coming out at 77MB is very unusual. Could you please send this document to the above email id.

Also, are you using any of the filters provided in the sample code, or there is no filter processing involved at all

Once again, thanks for your interest in XPS.

-Anish





Re: XML Paper Specification (XPS) XPSDrv Printer driver - Is it very slow?

Vijay Chauhan

Thanks for the update Anish.

I will send my results / document to xpsinfo.

-Vijay.





Re: XML Paper Specification (XPS) XPSDrv Printer driver - Is it very slow?

Vijay Chauhan

>>Also, are you using any of the filters provided in the sample code, or there is no filter processing involved at all

Forgot to write, but its "no filter processing involved".. That is NULL filter pipelineconfig file as,-

<Filter>

</Filter>

-Vijay