| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
| World Community Grid Forums
|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 11
|
|
| Author |
|
|
cchilaquil
Cruncher Joined: Apr 5, 2007 Post Count: 5 Status: Offline Project Badges:
|
So, my first suggestion is to throttle the grid agent, maybe to 20 or 30%, and see if that reduces or eliminates the problem. Other things to try are underclocking the processor, or running some really intensive hardware tests. Looking for a hardware fault that only occurs under maximum load can be very difficult. If this doesn't work, or you don't want to go to the trouble of further diagnosis, then please stop crunching on that machine. I'd hate for you to damage the computer or lose any data. Oh, and check the power supply. Sudden power spikes or loads are one of the few things that can cause a sudden reset. A final thought: you mention a map server. That implies some kind of GIS application, which probably uses some fancy graphics card features. The screensaver also kicks the grachics card into gear. Coincidence? Hi there, thanks on your answer. I have, well, diversified if to test different things. Two of the computers are running BOINC, as per the suggestion of Sekerob. So, far it seems to work fine, although I think eventually will begin to swap off quite a bit. Not a problem right now, and those computers are programmed for memory upgrade, anyway. I will set the other two computers in a low cycle, either underclocking or limiting UD to use 20-60% of cpu, and seeing how that works. Power supplies and fans where the first things I checked, as in the past similar problems have been due to heating and voltage artifacts [1]. The video cards are pretty simple and unsophisticated; that is, in fact, the reason for these computers use a map server: after receiving pertaining data, they calculate a vector (or in some cases a set of vectors), send this data to the mapserver, who interprets it in geo-spatial terms, and returns a single jpg showing the stuff. So, it implies just showing a jpg about 640x500. I was not aware that UD was using the net at others times besides sending/receiving results. I'll check network activity there, as in the past we have had problems with cpu and ram heating due to infinite or prolonged lapses where the computer is trying to send results and then calculating the very same results due to networks glitches. I appreciate your help, will keep posted on the results. Chilango Chilaquil [1] Including one involving "electrical cooling", a very nice concept that did not work on that particular computer because of a "faulty" earth. Our provider mentioned it was faulty, but then it was a very nice earth with less than 1 Ohm resistance. But I disgress. |
||
|
|
|