[FAD] Pause between jobs

[win2kuser]

I have noticed recently that I am getting a pause between wu's.

Sometimes it is only a couple of minutes, but it is normally 15-20 minutes that my pc's are sat doing nothing after they have completed a wu.

If I put Think in snooze, and then take it off, it will instantly start a new job so it's not as if it's post processing or something.

Yeah, it's nice to let the cpu cool off between jobs , but over time, that is an awfull waste of processing power.

Does anyone have any idea why, or if there is anything I can do.

Thanks in advance...




Mark.

Are you using a single queue server, or does each PC has it's own queue server running?

I really have no idea why it would be doing that, but it does trigger a deep, distant memory about something I read in the FAD forums in the past. Not exactly sure what, but give it time...

Cheers
Mick

[win2kuser]

Wow, thanks for the quick reply Mick.

Yep, my pc's each have a single queue. I keep meaning to get round to running a single queue, but never get time...

I had a quick look over on the fad forums, but didn't see anything obvious.

It is not all my pc's that are doing this, only the newer ones, XP2100 at 2.7, XP2600 and a XP2500 barton at 3.2.

The older slower machines keep up quite well.

Just looked at the queues for those machines and in the last 24 hours I have lost just over 3 hours in idle time

Strange...

I'll have a hunt around later at FAD to see if I can find what I think I remember.

have a feeling iot was about multi-threaded P4's though, and that obviously ain't your problem.

What OS is one each of these? They all win2k?

Cheers
Mick

[PresterJohn]

the last coupla days i've noticed similar delays on my home pc (dual p3 running w2k). i happen to be runing 2 instances of the think client...maybe that is it?!

i haven't really been monitoring my cows that closely so i don't know if this is happening with the others...

[win2kuser]

What OS is one each of these? They all win2k?

Wouldn't use anything but

[BitSpit]

It's due to the fact that the server only updates itself every 15 minutes. If the job goes by too fast, the next job may not be allocated when the current one is finished. The client may then also wait an additional 15-20 minutes.

[anki]

Bitspits right about the reason the way I get round the delay in server allocating jobs is to allocate the jobs manually.By the way Keith might be interested in any messages showing in server log regarding the effected jobs.

[Wizzard~Of~Ozz]

To correct this problem, Have the Queue open when the job completes.

QUOTE from Keith.

If you run with the server window open then the delay is short but otherwise server.exe can take 15 minutes to allocate a job (and in principle think.exe can take up to 20 minutes to check if there is a job allocated).

I use a queue server and have it open all the time so I get no delays, but if you run with the server hidden it can take up to 34 minutes from the time it hits 90% to get another job.

Another alternative is to allocate every job in the queue to the PC running it. (if you don't run a queue server and you want to have it minimized (hidden).

[win2kuser]

ah, new it would be something simple...


Thanks guys