| Title: | *OLD* ALL-IN-1 (tm) Support Conference |
| Notice: | Closed - See Note 4331.l to move to IOSG::ALL-IN-1 |
| Moderator: | IOSG::PYE |
| Created: | Thu Jan 30 1992 |
| Last Modified: | Tue Jan 23 1996 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4343 |
| Total number of notes: | 18308 |
I have a customer that is interested in migrating from PROFS to
ALL-IN-1 and TEAMLINKS. We went through an exhaustive demo with him
all week.
One of his questions was about the sender and fetcher.
By default the sender and fetcher jobs seem to resubmit themselves
every 15 minutes. He would like to shorten that time to say,
5 or 7 minutes, but he is worried about the overhead of the sender
and fetcher jobs resubmitting themselves and finding nothing to
send/fetch.
What can I tell him about the shortest amount of resubmit time for the
sender and fetcher jobs?
What can I tell him about the performance hit everytime the sender
and fetcher jobs run, but find 0 messages?
Normand Cardella
Montr�al
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2179.1 | no overhead | FORTY2::ASH | Grahame Ash @REO | Fri Jan 29 1993 17:36 | 12 |
Hi Normand, If you read the sender and fetcher command files (OA$LIB:OAMTISEND.COM, OA$LIB:OAMTIMAIL.COM) you can see that both the jobs check to see if there's any work to do before initialising ALL-IN-1. The sender runs the tiny sendcheck program, and the fetcher does a 'query' on the message Router mailbox. So, if you're worried about running up ALL-IN-1 unnecessarily, don't! In addition, I believe there are customisations around which allow you to run the jobs as detached processes - I'm sure someone will offer help . . . grahame | |||||