From: Till Kamppeter <till.kamppeter@gmail.com>
To: Tim Waugh <twaugh@redhat.com>
Cc: printing-architecture@lists.linux-foundation.org
Subject: Re: [Printing-architecture] IN 10 MINUTES: OP US/Europe - Tuesday 16 August 2011
Date: Wed, 17 Aug 2011 19:12:27 +0200 [thread overview]
Message-ID: <4E4BF67B.8030607@gmail.com> (raw)
In-Reply-To: <1313572289.2418.2.camel@localhost.localdomain>
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 prev parent reply other threads:[~2011-08-17 17:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-12 21:42 [Printing-architecture] Agenda - OP US/Europe - Tuesday 16 August 2011 Ira McDonald
2011-08-16 15:49 ` [Printing-architecture] IN 10 MINUTES: " Till Kamppeter
2011-08-16 16:42 ` Daniel Dressler
2011-08-16 18:08 ` Till Kamppeter
2011-08-17 9:11 ` Tim Waugh
2011-08-17 17:12 ` Till Kamppeter [this message]
2011-08-17 17:43 ` Daniel Dressler
2011-08-18 8:56 ` Tim Waugh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E4BF67B.8030607@gmail.com \
--to=till.kamppeter@gmail.com \
--cc=printing-architecture@lists.linux-foundation.org \
--cc=twaugh@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.