We've updated the server code on 171.64.122.74 to make it more responsive. We're keeping an eye on it to see for sure. One of the major differences is how long the server waits for a connection (it was waiting way, way too long before and that filled up all of its threads). We've cut that down as well as significantly increased the number of threads. In combination with no new assigns for this server for a while, this should drain it and get the server I/O back to normal.
« GPU2 server performance: update | Main | Windows/SMP client »
July 28, 2008
Comments
The comments to this entry are closed.
Recent Posts
- Blog moving to http://folding.stanford.edu/home/blog
- UPDATE 4: Planned server room maintenance: Monday, August 26
- UPDATE 3: Planned server room maintenance: Monday, August 26
- UPDATE 2: Planned server room maintenance: Monday, August 26
- UPDATE: Planned server room maintenance: Monday, August 26
- Reminder about aging cores (eg Core11, Core78)
- Planned server room maintenance: Monday, August 26
- A peek into Core 17 benchmarking
- New FAH web site
- Welcome to FahCore 17!
Still taking 3-4 attempts to get new WU's from this server... Not sure what you did solved the issue 100%, but at least we can get WUs versus having numerous GPUs idle. :)
Posted by: Sunin | July 30, 2008 at 07:56 AM
Right now I'm getting repeated failures to connect to the work servers to transmit results.
171.64.65.20
171.64.122.76
are failing to respond on either port 80 or 8080.
Posted by: Josh | July 30, 2008 at 12:49 PM
I am having repeated failures to upload results to 171.64.122.83:8080
The client has been attempting to upload since 06:29 GMT
Posted by: Frank | July 30, 2008 at 07:49 PM
Connections to upload have been failing all day long and I know it's not me or I couldn't be posting this.
Posted by: Steve | July 30, 2008 at 09:32 PM
IT KEEPS FAILING 4 Me 2 ??????????
Posted by: MNK | July 31, 2008 at 02:04 AM