lpsched

Wilfred Chau_1 — Fri, 15 Aug 2003 02:02:19 GMT

How many jobs can lpsched handle? If we have a few thousands jobs for lpsched to process per hour, will a 2-way L2000 with 2GB of ram be suffice?

We did a test and when these many jobs were submitted to the queues, CPU went from 60% to 80-90% utilized. Is it a normal performance hit? or Dose it have to do with networking?

Re: lpsched

Bhuvaneswari Selvaraj — Fri, 15 Aug 2003 03:45:04 GMT

There is actually no limits for the number of jobs that lpsched can handle. it indeed depends on the system's disk space.

For each printer, say test, a entry will be there under the
/var/spool/lp/request directory. When we submit a job to the printer, the file to be printed actually gets an entry in the /var/spool/lp/request/test dir.

For instance, if I print the passwd file using printer test and the size of the passwd file is 789 bytes, then

ll /var/spool/lp/request/test1 will show a file of size 789 bytes in it.

Ofcourse there will be additional changes also, but bare minimum this will be there. Hence, depending on the system free space and also on the job size, the number of jobs that lpsched can handle differs.

The CPU utilisation of the system will obviously go up, as the lpsched which is a daemon, needs to cater to all the pending printing requests and also the network traffic will also increase as the jobs get sent to the printer.

Hope this helps

topic lpsched in Operating System - HP-UX

lpsched

Re: lpsched