Overclock.net › Forums › Overclockers Care › Overclock.net Folding@Home Team › [Ubuntu] Setting up big-bigadv (P6903) for dedicated 2600k
New Posts  All Forums:Forum Nav:

[Ubuntu] Setting up big-bigadv (P6903) for dedicated 2600k - Page 10

post #91 of 771
The way that I use to determine if I am running at 100% is top. Open up the terminal and type in "top", it will give you a list of all processes and how much cpu each is using. Normally my 2600K is at 797% for fah.
 
TC folding
(7 items)
 
 
CPUMotherboardGraphicsRAM
2600K Asus Gene-z MSI 570 Ripjaws X Series 8GB 1600MHz 
Hard DriveCoolingOSPower
OCZ Vertex 3 XSPC Raystorm Block + 180mm Radiator Windows 7 Ultimate/Ubuntu 10.10 Corsair 750TX 
Case
Silverstone TJ08-E 
CPUMotherboardGraphicsRAM
2600K Sabertooth P67 ATI 4650 GSkill 2133 2x2GB 
CoolingOSCase
XSPC Rasa, RX240 Ubuntu 10.10 Fractal Midi 
  hide details  
Reply
 
TC folding
(7 items)
 
 
CPUMotherboardGraphicsRAM
2600K Asus Gene-z MSI 570 Ripjaws X Series 8GB 1600MHz 
Hard DriveCoolingOSPower
OCZ Vertex 3 XSPC Raystorm Block + 180mm Radiator Windows 7 Ultimate/Ubuntu 10.10 Corsair 750TX 
Case
Silverstone TJ08-E 
CPUMotherboardGraphicsRAM
2600K Sabertooth P67 ATI 4650 GSkill 2133 2x2GB 
CoolingOSCase
XSPC Rasa, RX240 Ubuntu 10.10 Fractal Midi 
  hide details  
Reply
post #92 of 771
Quote:
Originally Posted by JoshHuman View Post
The way that I use to determine if I am running at 100% is top. Open up the terminal and type in "top", it will give you a list of all processes and how much cpu each is using. Normally my 2600K is at 797% for fah.
Well look at that... The resource monitor doesn't work, but that'll tell you what's up...

Thanks JoshHuman!
post #93 of 771
Got a couple errors:

Quote:
[19:14:47] Completed 250000 out of 250000 steps (100%)

Writing final coordinates.

Average load imbalance: 15.5 %
Part of the total run time spent waiting due to load imbalance: 5.1 %
Steps where the load balancing was limited by -rdd, -rcon and/or -dds: X 0 %

NOTE: 5.1 % performance was lost due to load imbalance
in the domain decomposition.
And about 5 of these..

Quote:
[20:19:22] + Attempting to send results [July 11 20:19:22 UTC]
[20:19:22] - Couldn't send HTTP request to server
[20:19:22] + Could not connect to Work Server (results)
[20:19:22] (171.67.108.25:8080)
[20:19:22] + Retrying using alternative port
[20:19:22] - Couldn't send HTTP request to server
[20:19:22] + Could not connect to Work Server (results)
[20:19:22] (171.67.108.25:80)
[20:19:22] Could not transmit unit 01 to Collection server; keeping in queue.
[20:19:22] + Closed connections
So is just my stats didn't load or none of the folding and stats were uploaded?
post #94 of 771
it seems that Langouste is preventing WU's from being actually submitted. The only way I could submit a wu was to disable Langouste and remove the proxie settings from the Fah config file.
post #95 of 771
Quote:
Originally Posted by AMD SLI guru View Post
it seems that Langouste is preventing WU's from being actually submitted. The only way I could submit a wu was to disable Langouste and remove the proxie settings from the Fah config file.
And enable it for the next one.....well this sucks..
post #96 of 771
No... keep an eye on your langouste. The FAH client will error out because it can't communicate with the servers. This is normal. Langouste is working in the background.

FAH will try several times in quick succession to upload, then decide to keep it in queue and download a new wu. While this was happening, Langouste was doing it's job (if it was set up right.) I has to be set up exactly like the guide says.
post #97 of 771
Quote:
Originally Posted by mach1 View Post
No... keep an eye on your langouste. The FAH client will error out because it can't communicate with the servers. This is normal. Langouste is working in the background.

FAH will try several times in quick succession to upload, then decide to keep it in queue and download a new wu. While this was happening, Langouste was doing it's job (if it was set up right.) I has to be set up exactly like the guide says.
Might have to just start over then...had a power outtage and my UPS didn't kick in for some reason. I'll check it when I get home. How long will it keep it in queue?
post #98 of 771
Quote:
Originally Posted by mach1 View Post
No... keep an eye on your langouste. The FAH client will error out because it can't communicate with the servers. This is normal. Langouste is working in the background.

FAH will try several times in quick succession to upload, then decide to keep it in queue and download a new wu. While this was happening, Langouste was doing it's job (if it was set up right.) I has to be set up exactly like the guide says.
well that is news. lol I did some research on Langouste just to find out what in the world it actually is.

Langouste is actually a program that helps download and upload new WU's without waiting the extra hour or 2 for the F@H client to do it.

I'm sorry if I lead you astray Wrecking Crew. I'll keep my mouth shut.
post #99 of 771
Quote:
Originally Posted by AMD SLI guru View Post
well that is news. lol I did some research on Langouste just to find out what in the world it actually is.

Langouste is actually a program that helps download and upload new WU's without waiting the extra hour or 2 for the F@H client to do it.

I'm sorry if I lead you astray Wrecking Crew. I'll keep my mouth shut.
Nah... it just gave us a chance to clarify Be sure to check your langouste window. If it is full of errors that don't look right (there are some that are normal, i've found... like saying that more than one instance is running) then something is wrong and you'd better start over.

And WC, I don't know how long it will hold a wu in queue...
post #100 of 771
Quote:
Originally Posted by AMD SLI guru View Post
well that is news. lol I did some research on Langouste just to find out what in the world it actually is.

Langouste is actually a program that helps download and upload new WU's without waiting the extra hour or 2 for the F@H client to do it.

I'm sorry if I lead you astray Wrecking Crew. I'll keep my mouth shut.
Not at all man, we're all learning new things. I appreciate all the help I get from everyone here.

Quote:
Originally Posted by mach1 View Post
Nah... it just gave us a chance to clarify Be sure to check your langouste window. If it is full of errors that don't look right (there are some that are normal, i've found... like saying that more than one instance is running) then something is wrong and you'd better start over.

And WC, I don't know how long it will hold a wu in queue...
I've had that error too...the more than one instance. I'll go home and see what I can do, if not, then i'll just redo the whole thing. Hope I can figure it out and it'll send the progress made on that WU in time. Thanks for the help.
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Overclock.net Folding@Home Team
Overclock.net › Forums › Overclockers Care › Overclock.net Folding@Home Team › [Ubuntu] Setting up big-bigadv (P6903) for dedicated 2600k