[Printing-architecture] IN 10 MINUTES: OP US/Europe - Tuesday 16 August 2011

Daniel Dressler danieru.dressler at gmail.com
Wed Aug 17 17:43:35 UTC 2011

Without compression the full compiled ppd set is about ~220MB, with pyppd it
gets down to ~330KB.


2011/8/17 Till Kamppeter <till.kamppeter at gmail.com>

> On 08/17/2011 11:11 AM, Tim Waugh wrote:
>> On Tue, 2011-08-16 at 20:08 +0200, Till Kamppeter wrote:
>>> Thank you. Using pyppd-compressed PPD archives the listing of the PPD
>>> files take well less than a second on my computer and extracting the
>>> mentioned PPD file takes the same order of magnitude of time as SQLite.
>>> For most CUPS users the pyppd solution is the best due to the speed.
>> I'm not sure I really understand the purpose of pyppd.  Is it just to
>> save disk space?  CUPS implements its own fast indexing of PPD files, so
>> performance seems to be covered there.
> For ready-made (static) PPDs, like the ones from the printer manufacturers
> for PostScript printers, it is only saving disk space. Putting them all into
> one archive compresses them much more than individually gzipping them.
> Replacing PPD generators like /usr/lib/cups/driver/foomatic by
> pyppd-generated PPD archives is also a vast improvement in speed. It is much
> faster to grab a PPD out of a compressed archive then putting it together
> from the Foomatic XML data.
>   Till
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.linux-foundation.org/pipermail/printing-architecture/attachments/20110817/e4b48a1c/attachment.htm 

More information about the Printing-architecture mailing list