[FaD] Think taking 92-95% of CPU cycles

[vserlnv]

I just turned in 12 -15 results.

I also turned Think off on 6 or 7 machines.

I am heavily into UD, and run UD at the same time as Think ( FaD ). The machines, I shut Think down on, have 2+GHz processors, and UD WU's are at 70-120 hours, and 42 or 56 or 48% ( etc.)!? I don't think so! When I looked at Task Manager, Think is consuming all but 2-3% of available cycles.

That won't do. Kinda sux. I like being on this team, but I can't have FaD shoving UD aside. Up until this last Think update, FaD and UD happily shared the CPU. Now FaD damn near wants it all.

Sorry, but expect to see my production to drop. I'll keep an eye on the others. If they share 50-50 or so, I'll let FaD run.

I didn't sign up for FaD to basically kill UD production.


Scott

I was putting out like 13k per day. Things are dropping.

Last 5 days of UD production -
11,999 10,232 11,654 10,852 7,914

I expect today's output will drop right through the floor...

[BitSpit]

The whole point of the new version was to fix CPU priority problems. However, it seems to have caused problems instead of fixing any. Anyway, just add the line THINK_PRIORITY=NORMAL:IDLE to think.env and things will be behave like the previous version (as in the server program is actually responsive )

[vserlnv]

I went to FaD forum, read the entire thread concerning this. There are people, I think Sharder is one of them, who have had mixed results with that entry. I'm not real into editing config files, especially on 17 different machines.

So someone please let me know when they have a new version out, or whatever, and I'll do an uninstall/reinstall.

I posted in that thread.

http://forum.find-a-drug.com/viewtop...r=asc&start=60

[PresterJohn]

i wasn't even aware that they had released an new verson, L.

considering the problems i had with K, i really think the fad people need to better beta test and consolidate releases. it may seem like moving forward when you release a new version (with added features?) every 6-8 weeks, but heaven help you if you find incompatibilites with the new client. for crunchers that run FAD on many machines, we simply don't have the time & energy to troubleshoot any new problems.

of paramount importance should be getting new versions really tested...perhaps offer both the production and beta versions in parallel for at least 3 months before phasing out the old client.

[sharder8]

Originally posted by vserlnv
I went to FaD forum, read the entire thread concerning this. There are people, I think Sharder is one of them, who have had mixed results with that entry.

I still haven't figured out why, but the PIII is continuing to show marked improvement. The PII dropped off untill I removed the lines I added to the *.env. The 800 and 950MHz Athlons seem to show some improvement. And finally, the 1.3GHz is doing fine, once I removed Diskeeper Lite. I suspect that Diskeeper Lite caused a huge jump in the cpu/process queue's that caused a major slow down when it went to start. Note: There hasn't been any problem between Diskeeper Lite and any of the other machines, only the one running the 1.3GHz Athlon.

On a side note, I was talking to a gentleman today that is pretty heavy into computer engineering and he mentioned that some of the Athlon's (namely the 1.3GHz) had some problems in the way they handle cpu and process queue's, specifically priorties. I got his # and will try to learn more later and report back.

Hate to see ya' shutting [FAD] down on any machines Zippy, but then again, that'll give some of us a chance to catch up!

I suspect Keith is working hot and heavy on fixing this problem, and I seen he has had some offers from some sharp people to get this fixed quickly.

Harder

[Wizzard~Of~Ozz]

Zippy, Sorry to hear that, I'm currently running at IDLE:IDLE and have had no problems (this includes my mail/FTP and webserver/Fad Queue server)

If anyone has the old version of Think.exe (1.21k) and can send it to you it will revert Think to how it was for you.

[vserlnv]

Yep, UD took a serious nosedive last night. You can see why I'm concerned.

06/16/2003 0:007:00:49:19 4,509 6
06/15/2003 0:010:23:37:12 7,914 10
06/14/2003 0:018:12:37:22 10,852 11
06/13/2003 0:019:11:51:07 11,654 17
06/12/2003 0:013:12:09:10 10,232 16
06/11/2003 0:014:20:34:44 11,999 19
06/10/2003 0:017:16:43:33 12,771 18
06/09/2003 0:016:22:50:51 12,156 20
06/08/2003 0:017:10:58:41 13,240 22
06/07/2003 0:018:17:38:45 11,882 19
06/06/2003 0:024:10:25:49 17,253 25
06/05/2003 0:014:15:14:01 11,285 19
06/04/2003 0:019:13:58:08 14,515 24
06/03/2003 0:015:15:02:08 11,551 20


I'm a serious packrat, and I'm sure I have K around here somewhere, however I'm not sure I follow you on how that would make it workright.
Should I just totally uninstall, then install K? Wouldn't FaD just update itself to "L" once I installed K, anyway.

then again, that'll give some of us a chance to catch up!

LOL, that's what I was thinking.

[vserlnv]

Decide to try the edit Keith suggested.

Anyway, I just made the entry in the think.env file you suggested, Keith (THINK_PRIORITY=IDLE:IDLE ). Only edited the file on two of the machines so far, but Task Manager shows FaD and UD are once again playing nice together, roughly 50/50. The server window snaps in to place when I bring it up, also, instead of taking way too long to be drawn.

I need to go to work, I'll edit that file on the rest later. It'll give my teammates a little respite.

Thank you.

Scott

As long as it is back to normal, I'm okay. Guess, editing the files is not that big of a deal. Thanks for the help, you guys.




Crunching to Crush Cancer!

Somebody, Stop Me!

[vserlnv]

Got about half the machines' think.env files edited. Should be back up to normal tomorrow. Short break.

[Wizzard~Of~Ozz]

Good work, are using VNC for your machines? do they have floppies, why not just copy the file to each PC then restart FaD on them, it will start with the new settings, or if they are networked, edit one, then execute think.exe and tray.exe from a mapped drive.

Set FaD directory to be shared as fad
map that drive on each PC.
create shortcut to think.exe and tray.exe in the mapped drive to startup.

Then they all run from one Queue and are easier to control and sending jobs is all done from one PC.

You also gain processor time from less overhead (queue not running on all machines)

Only downside if the Queue server goes down, it takes them all with it. but it's sounds like your machines are all well maintained.