[FaD] Happens only to me?

[eagle1]

Hey FaD guys!

I have a question.... Is the FaD client having problems?
I mean, one of my clients has been stuck on a WU for 2 days on the same % with the same hits and all. Is the D2OL thing happening again? (stuck wu's?). IS it the client?
This seems to be happening on 2 machines and both of them with the same components:

P4 1.7
128MB PC133 Ram
bla bla bla...

They have never given me problems until now.! My T-Bird 1.2 keeps crunching away and that's why my production has been down... !

If this keeps happening, I'm afraid I'm going back full to genome or ecc2.

[RustyGT]

Agreed eagle!

I've got "1bzh" jobs gone 6,7,8 Days on my 1.3G 256M Box.

Same on my .9G 256M box. Ten Days?!

"Auntie Mickwish" says: 'Dont kill the long jobs!'

OK Auntie!

So why do my "little" boxes rattle out results?
Cos I said they "were", in the control panel.

UD used to give points for long jobs.

FaD needs to address this soon.

R.

[Wizzard~Of~Ozz]

I've found some jobs (%) take a very long time for near hits, if you want to check if it's actually moving do this.

View graphics, then hit job info.

In the job info window You will see current molecule.

In there there is a m# after the # sign the first # counts from 0-100 (this is the %) after the - counts from 100-0 if this number is no longer moving then you have a problem, however each of these numbers times out after 60 minutes to prevent think.exe from sitting on a molecule for a long time.

Also if you have any 1BZH-Q4's in queue kill them, remove them all from queue, they are discontinued because they tak 3 days on an Athlon XP2000. They were replaced with 1BZH-Q5's which are much faster.

[eagle1]

OHhh.. ok.. I just never had a long job like that just stay there without changing % or hits for days. The long jobs I have had at least show a change of % or hits after a day!

Ok.. thanks for the info WoO and Rusty!

[Rovastar]

The pecentage bar isslow look at the job info and see if the individual jobs are updating.

e.g m1234~97-34

The last number should go down from 100 to 1 (the second one goes up until 100 hence the around 10,000 mark mols per job) . If theyt are taking agaes it should hope every hour or so when the mols will timeout if they cannot complete.

So check back after a few hours to see if this number has changed.

The percentage only updates every 100 mols (when the middle number changes)

I have already got this issue on the wishlist with THINK at FAD.

[Rovastar]

Oh you already have this info.Note toself: read the thread properly

[Wizzard~Of~Ozz]

Hey rovastar, where you been you haven't sent in anything in quite a while.

[Wimpler]

Well, if you don't run the long molecules, somebody else will have to do it again

The problem with the long 1BZH-Q4 jobs issolved now, so they shouldn't cause to much problems either.

I think the great variety in CPU time required for a job is the only negative thing about FaD. But for me, that doesn't change the fact it's the best project

[sharder8]

What Wimpler said!

Harder

[eagle1]

Yeah.. I left them running because they are not stuck!! I thought they were but the job info informs me otherwise so... I'll let the machine crunch until it's finished.
The thing is that I already queued a lot of these molecules and that's why my production is down because they take too long. They have to fix their scoring though!