You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The currently recommended approach for encoding binary data in PPD files through PPD: messages from a filter suffers serious performance issues when the amount of data becomes large. Even more so when the PPD file is large.
Each PPD: message causes the PPD file to be read by line and written to a copy. If a filter emits 10s or 100s of messages this can result in 10s or 100s of megabytes of disk access, which can make the scheduler non-responsive. On OS X, this can lock the application and deny service to concurrent users.
While concise encoding, compression and multiple attributes per PPD: message help reduce the impact, the problem remains unsolved.
The text was updated successfully, but these errors were encountered:
Version: 1.6-current
CUPS.org User: chulbert
The currently recommended approach for encoding binary data in PPD files through PPD: messages from a filter suffers serious performance issues when the amount of data becomes large. Even more so when the PPD file is large.
Each PPD: message causes the PPD file to be read by line and written to a copy. If a filter emits 10s or 100s of messages this can result in 10s or 100s of megabytes of disk access, which can make the scheduler non-responsive. On OS X, this can lock the application and deny service to concurrent users.
While concise encoding, compression and multiple attributes per PPD: message help reduce the impact, the problem remains unsolved.
The text was updated successfully, but these errors were encountered: