UBE Queue Delay

Hi List,

I have a query regarding the setting of QueueDelay in the JDE.INI on the servers. Currently we have a large number of jobs which typically take 1-5 seconds to process and then the queue sits for quite a while before the next job comes in. WE have QueueDeley set to 30 in our JDE.INI and I wonder what are the implications of changing this to a much lower number e.g. 10.

Thanks for any help.

The queue delay is the frequency of the queue looking at the submitted
jobs and seeing if there is a job in the wait state for the particular
queue name. I have changed ours down from 30 to 5. The job's wait is now
shorter before it goes into processing. The negative is that it takes a
little processing for the system to constantly query the table to see if
anything is waiting, but for our system the compromise was more than
worth it..

John

----------------------------------------------------------
OneWorld Xe (B733.3)
Update 6, SP 19.1_B1
Running on: WIN2K/SP2, SQL2k/SP2
Metaframe 1.8a
----------------------------------------------------------





Xe, Update2, SP16
SQL2k, Win2k
Metaframe 1.8a

I usually change it to 5. Heck, you could change it to 1 if you really wanted. The only down side I know of is that the database will be queried once per second for waiting jobs.

It just queries the job status table at the interval defined in the ini file,
so unless your job status table is huge or your enterprise server is
performing badly, it should have minimal impact setting it to a lower value
Regards
Kieran Fitzgerald

Andrew, I faced the exact same situation some time ago and we reduced the
Q-delay value to 10 seconds. We are having about 30 UBE queues running on
our server and we have seen no drawbacks after this change. Only, the
jobs don´t pile up any more.
By the way, the default q-delay on Unix boxes is 5 seconds!
My client has a 4-way (Xeon, 750 Mhz) Oracle database server. We run 1000-
2000 jobs per day. We keep the jobs for about a week in the job master
table.
Our DBA did some tuning to keep the job master table always in memory.

Hope this helped, Gerd