home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!mcsun!Germany.EU.net!gmd.de!jvnc.net!darwin.sura.net!mips!swrinde!elroy.jpl.nasa.gov!decwrl!decwrl!infopiz!mccall!ipmdf-newsgate!list
- From: bob@camb.com (Bob Tinkelman)
- Newsgroups: vmsnet.mail.pmdf
- Subject: RE: pmdf 4.1-4 and slow delivery
- Message-ID: <01GNWXGQ9PXI000ACN@Eisner.DECUS.Org>
- Date: 23 Aug 92 12:36:15 GMT
- Sender: Bob Tinkelman - CCA <TINKELMAN@Eisner.DECUS.Org>
- Organization: Cambridge Computer Associates, Inc.
- Lines: 15
- Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
- Resent-Date: 23 Aug 1992 08:36:15 -0400 (EDT)
- Resent-From: epmdf@YMIR.CLAREMONT.EDU
- CC: info-pmdf@INNOSOFT.COM, TINKELMAN@Eisner.DECUS.Org
- Errors-To: epmdf@YMIR.CLAREMONT.EDU
- Resent-Message-ID: <01GNWRVH25DU94E3LB@INNOSOFT.COM>
- X-Vms-To: in%"tkslen@ubvms.cc.buffalo.edu"
- X-Vms-Cc: in%"info-pmdf@innosoft.com",TINKELMAN
- Mime-Version: 1.0
- Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
- Content-Transfer-Encoding: 7BIT
-
- This is probably not your problem, but it was something that surprised us.
-
- PMDF 4.1 can use many more batch jobs than 4.0. If you're not using the
- process symbiont, that could make a performance difference. In versions
- prior to 4.0, the periodic delivery job would, if it was running in the
- appropriate batch queue for a channel, run the channel itself, rather than
- submitting a separate batch job for that channel. With 4.1, it always
- submits a separate batch job.
-
- When I installed 4.1 on eisner.decus.org, the number of batch jobs run (on
- the whole system) went up from about 800/day to about 1250/day. [The
- configuration here at that time did no immediate delivery; all delivery was
- from the periodic delivery job, running with a post interval of 10 min.]
- --
- Bob Tinkelman <bob@camb.com>
-