![]() |
|
#1
|
|||
|
|||
|
sluggish performance
on some w/u's i stay at around 600-700 ns/day , but it seems like every 2-3 w/u tht it gets like super sluggish and is the 30 ns/day range, it does that for the entire length of the unit. normally takes me around 45min to an hour to get an average unit done, but the sluggish ones take like 4-5 hours or more. what is causing that? happening to any1 else?
|
|
#2
|
|||
|
|||
|
Are you processing different units, or are these the same vintage? Some units are worth small amounts of points (i.e. 353 points) and process fast, while others are worth more points (i.e. 1920 points) and can take longer to process. Which units are you referring to as being sluggish?
|
|
#3
|
|||
|
|||
|
the 1888 point WU's take 5-7 hours depending on your gfx card.. 737 or what ever point they are worth take 3-4 hours and the rest take any where from 1-3 hours..
|
|
#4
|
|||
|
|||
|
I suggest that you don't use the viewer to monitor your client and instead download a program like HFM.NET or Fahmon to monitor it instead. Those programs will tell you lots of useful info, like percentage progress for the current workunit, the points value of the current workunit, your current points per day average based on the amount of time it takes for you to finish one percent of the unit, etc. I suspect that you're simply running different-size workunits as has already been suggested, and using a monitoring program will tell you for certain whether or not that is the case.
|
|
#5
|
|||
|
|||
|
Quote:
|
|
#6
|
|||
|
|||
|
ok, let me clarify a little bit more, the system is a dedicated folding rig, a c2q q6600 2.4 oc'd to 3.2 on air, never breaks 42-45 c under load on any of the cores, temp from hwmonitor from the chip itself, not the winbond, proc reads like 10c higher than the others. the gpu is a bfg gtx280 oc, it is mildly overclocker above what it came as, and 4gb or corsair ram. running win 7 ult 64bit. i don't know how to tell what type of w/u im getting but i do notice the sizes are different on the regular display window, seems the bigger ones work just fine and on the "performance" line give out around 600-650 ns/day on average. but others even if thery are the same size only get 200-300ns/day and the graphic is slow and jittery, wheras when its at 600-650ns/day its jst flipping around like normal. is there any way to keep it on the faster ones? and another thing, when its on the ones taht are slower ns/day it doesn't use as much resources and it doesn't heat up like normal, and it takes a whole lot longer.
|
|
#7
|
|||
|
|||
|
its not the process time thats bothering me, its the performance of the w/u itself. reguardless of size, from 8000000 to 20000000 it performs at 600-650 ns/day. and does those in like an hour and the system stays maxxed out and gpu is a balmy 65-66c. BUT on some w/u's they only run at 150-300ns/day system is far from fully loaded, temps go way down to around 50-55c and it takes like 3+ hours.
|
|
#8
|
|||
|
|||
|
first off.. like zero said.. stop using the built in display window and use a monitoring program like fahmon, fahspy, or HFM.net.. that will give you better answers into why certain WU's are slower then others.. the built in display for F@H GPU effects the performance of the card folding.. and not just by a little bit it can cut speeds on some work units in half where as some it doesnt effect them..
so until you start using a separate F@H monitor theres not much else we can help you with since none of us use the built in display..
|
|
#9
|
|||
|
|||
|
The built-in viewer is worthless. Stop using it and use a real monitoring program instead.
Sorry for the emphasis, but you didn't seem to notice the first time I said it.
|
|
#10
|
|||
|
|||
|
well, my next ? was going to be on which one to use and how to set it up, this is the first time ive used F@H so i don't know much about it, never thought id have to apologize for being a noob at something, lol
|
|
#11
|
|||
|
|||
|
Which one you use is largely a matter of preference. I personally prefer HFM.NET as it is the most feature-packed and customizable of the monitoring programs. Fahmon is the most popular, although HFM.NET has a very similar interface with more options.
|
|
#12
|
|||
|
|||
|
ok, got hfm.net it says the one im doing is 1888 credit, i just don't understand why it doesn't stress the gpu as hard as the lower credit ones. i guess it's not for me to know
|
|
#13
|
|||
|
|||
|
Even different workunits with the same point values can stress the GPU differently. It depends on the specific workunit and the kinds of calculations being done. More than that I can't say because I don't know. But the real number you have to pay attention to is the PPD, since that is the best measure of overall performance. As long as you aren't seeing any major fluctuations in that number, you're good to go.
|
|
#14
|
|||
|
|||
|
i take it there aren't any that have a display similar to the default one that has the protein model on it? i know it serves no real purpose, but fun to look at from time to time. i didn't realize until i quit using it tht it was the prog that was fully loading my 4th core to 100% when its not on, my cpu usage is near 0. but the gpu is still doing its thing. can i run more than just the one gpu client?
|
|
#15
|
|||
|
|||
|
o, my ppd is currently at 6347.206
|
|
#16
|
|||
|
|||
|
Quote:
|
|
#17
|
|||
|
|||
|
i was going to setup a dual boot ubunti win7 on here, so i guess when i get that done i will, would it be feasible to run the smp client and the gpu client? or the gpu and 2-3 of the uniproc clients (leaving 1 core for random use) if using the smp client is the best, which of them is the better one, i seen there are guides for 2 different smp clients.
|
|
#18
|
|||
|
|||
|
You can run the SMP and GPU clients at the same time. And like I said, the best way to go is to use a Linux VM and run the Linux SMP client. You can find the guide to doing that here: http://www.hardforum.com/showpost.ph...3&postcount=19
|
|
#19
|
|||
|
|||
|
lol at large text
|
|
#20
|
|||
|
|||
|
![]() |
| Thread Tools | Search this Thread |
|
|