kmcevoy
Member
We process 2000-3000 orders per day. We ship confirm each order, generate
and print the invoice at the warehouse packing stations, and put the invoice
in the box with the shipment. We use WTS in 6 of 7 locations. For the
WTS locations we have to generate the invoice by submitting a batch job.
The process works fine until the queues start to backup. The busiest time
of the day is in the afternoon. The users will report that the invoice
jobs submitted to the queues are backing up. When we check the queues,
sure enough there are numerous jobs in a Wait status. When everything is
running normally, generating a single invoice will take a few seconds. We
setup a multi-threaded queue that allows 6 jobs to process at one time. When
things are running normally we rarely see more than 3 jobs running at a time
because they get processed so quickly. When the queues backup, it appears
that only 1 job will process at a time (acts like it is single threaded) and
its execution speed is a little slower. The queue service delays before
processing the waiting jobs and then treats the queue as single threaded.
No database locks are being held when this problem occurs. Enterprise
server performance is not slow at this time. Interactive users don't
notice any performance problems.
We have done the following to try to alleviate the problem:
- We drop and rebuild the F986110 table on a weekly basis. We analyze the
table and rebuild the indexes several times a day.
- While a backup is occurring, we do an analyze on the F986110 table and
sometimes the slowness goes away immediately, sometimes it doesn't.
- Every morning, we delete the completed jobs from the previous day. We
usually create about 2500-3500 jobs per day.
- The queues run on the enterprise server and it gets rebooted every night.
- Sometimes we can cycle the queue services and the problem goes away.
Sometimes the problem comes right back. On the really bad days we have had
to reboot the server.
- We can move a waiting job to a different queue and it may process
immediately; sometimes it waits before processing.
Has anyone encountered this kind of problem before? Any suggestions on
what else to check? Any feedback would be greatly appreciated.
Thanks,
Kevin McEvoy
J.A. Webster, Inc.
[email protected]
B733.2, SP11.1, NT, Oracle 8.05
and print the invoice at the warehouse packing stations, and put the invoice
in the box with the shipment. We use WTS in 6 of 7 locations. For the
WTS locations we have to generate the invoice by submitting a batch job.
The process works fine until the queues start to backup. The busiest time
of the day is in the afternoon. The users will report that the invoice
jobs submitted to the queues are backing up. When we check the queues,
sure enough there are numerous jobs in a Wait status. When everything is
running normally, generating a single invoice will take a few seconds. We
setup a multi-threaded queue that allows 6 jobs to process at one time. When
things are running normally we rarely see more than 3 jobs running at a time
because they get processed so quickly. When the queues backup, it appears
that only 1 job will process at a time (acts like it is single threaded) and
its execution speed is a little slower. The queue service delays before
processing the waiting jobs and then treats the queue as single threaded.
No database locks are being held when this problem occurs. Enterprise
server performance is not slow at this time. Interactive users don't
notice any performance problems.
We have done the following to try to alleviate the problem:
- We drop and rebuild the F986110 table on a weekly basis. We analyze the
table and rebuild the indexes several times a day.
- While a backup is occurring, we do an analyze on the F986110 table and
sometimes the slowness goes away immediately, sometimes it doesn't.
- Every morning, we delete the completed jobs from the previous day. We
usually create about 2500-3500 jobs per day.
- The queues run on the enterprise server and it gets rebooted every night.
- Sometimes we can cycle the queue services and the problem goes away.
Sometimes the problem comes right back. On the really bad days we have had
to reboot the server.
- We can move a waiting job to a different queue and it may process
immediately; sometimes it waits before processing.
Has anyone encountered this kind of problem before? Any suggestions on
what else to check? Any feedback would be greatly appreciated.
Thanks,
Kevin McEvoy
J.A. Webster, Inc.
[email protected]
B733.2, SP11.1, NT, Oracle 8.05
