[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#665435: marked as done (cups: too much memory consumption in default configuration (swaps out, brings print server to a crawl))

Your message dated Sat, 4 Jan 2014 13:53:33 -0800
with message-id <20140104215333.GD12251@google.com>
and subject line Re: cups: too much memory consumption in default configuration (swaps out, brings print server to a crawl)
has caused the Debian Bug report #665435,
regarding cups: too much memory consumption in default configuration (swaps out, brings print server to a crawl)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
665435: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665435
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: cups
Version: 1.5.2-8
Tags: upstream

Hi,

Trying to use cups with the hpcups driver as a print server, I found
that printing anything (e.g., a test page) with nothing else happening
would slow the server to a crawl.  "top" shows gs using 200 MiB or so
of address space, with ~130 MiB resident; "free" shows nonzero swap
usage but not terrible.   This machine has only 150 MiB of RAM to work
with, so anything more than 100 MiB is a lot of memory for one
application to ask for.

With "RIPCache 16m" in /etc/cups/cupsd.conf the system seems to be
sane again and printing is still working fine.

changelog.Debian.gz says

 cups (1.4.1-2) unstable; urgency=low

   * Add dynamic-default-ripcache-size.dpatch: Replace above functionality by
     setting the internal default value of RIPCache to MemTotal/4, if not given
     in the configuration file.

which sounds promising, but then I see the actual code:

  cupsdSetString(&RIPCache, "128m");

Perhaps this functionality was ripped out.

Intentional?

Thanks for making printing on Linux possible.

Sincerely,
Jonathan

--- End Message ---
--- Begin Message --- 
Didier 'OdyX' Raboud wrote:

> Now, 128Mb is arguably a lot of memory, but I think that assuming that 
> this much can be allocated is a reasonable expectation that CUPS makes 
> there.

I disagree, but closing anyway as I think any Debian-specific work on
this is unlikely to improve anything.

Thanks,
Jonathan

--- End Message ---
Reply to: