Problems and Technical Issues with Rosetta@home
Message boards : Number crunching : Problems and Technical Issues with Rosetta@home
Previous · 1 . . . 335 · 336 · 337 · 338
| Author | Message |
|---|---|
|
Sid Celery Send message Joined: 11 Feb 08 Posts: 2356 Credit: 44,909,866 RAC: 25,960 
|
Event log today: Steve, take a look at kotenok2000's message above The lines I've extracted from your log tell me the change you've made in your hosts file isn't being read by your PC. "hosts" can't have any extension at all, such as hosts.txt. hosts.doc, hosts.bak or hosts.old It has to simply be "hosts" When you showed us the hosts edit you made, it looked good to me, but if the filename is wrong, that's the only explanation I can see for "Server error: feeder not running" still being reported in your log file. That's the line we have to get rid of.  
|
|
Stevie G Send message Joined: 15 Dec 18 Posts: 124 Credit: 1,019,690 RAC: 731 |
Event log today: Sid, Tom, et al: Guess what?? Today I initially got two Rosetta tasks!! Then a few hour later, lo and behold, I got NINE tasks! All due by June 3, but running between 183 -187 degrees F. My cut-off temp is 190 F. So it looks like things have returned to something resembling normality. We'll see how long it last. I want to express my sincere thanks to you both and all the others who helped me get through these tribulations. S. Gaber Oldsmar, FL |
|
Tom M Send message Joined: 20 Jun 17 Posts: 140 Credit: 30,602,375 RAC: 102,732
|
Tom: I have only been able to get rid of that message by NNT tasks on other projects for extended periods so your total tasks in cache goes down significantly. A day or two may not be long enough. Proud member of the O.F.A. (Old Farts Association) |
|
Tom M Send message Joined: 20 Jun 17 Posts: 140 Credit: 30,602,375 RAC: 102,732
|
Sid,
The deadline I am seeing is currently June 2. So I believe I am getting 3 day deadlines. ===edit== And dropped the cpu tasks allowed for Rosetta (in the Pandora config file) to 200. For a while, a cache under 300 seemed to not be producing expired tasks. And I don't want to have tasks being expired. The problem is to keep more than 120 processing at once while not taking more than 3 days (I think) to get them done. Your previous calculations seem to think that 12 hour tasks should manage to do that for a cache of 300 or under. 3 x 120 = 360. I started up my polling script when I hit some 90 Rosetta tasks processing and my backup cpu project started downloading tasks. <scratch head> :) ===edit== I looked at the list of canceled by server tasks. They were all canceled the same day they were sent. So they were not even getting to the 3 day deadline and being canceled. Proud member of the O.F.A. (Old Farts Association) |
 Grant (SSSF)Send message Joined: 28 Mar 20 Posts: 1848 Credit: 18,534,891 RAC: 0 |
I note that several tasks were cancelled before starting, despite a 2-week deadline.Those Tasks were all from the beginning of last month/the end of the previous month. Current Einstein Tasks appear to be getting done within 1.5-2 days. I looked at the list of canceled by server tasks. They were all canceled the same day they were sent. So they were not even getting to the 3 day deadline and being canceled.Cancelled by server Tasks are Tasks that have been resent because they hadn't been returned by the deadline, but ended up being returned by that other system before your system started processing them; so the project cancelled those resends as they were no longer needed. The lager your cache, then the more often that will occur. Grant Darwin NT |
|
Stevie G Send message Joined: 15 Dec 18 Posts: 124 Credit: 1,019,690 RAC: 731 |
Tom: Tom: Today and yesterday, my computer processed 13 Rosetta tasks! Right now it's working on 16 more. But I have to suspend most of those because it was running at 202 degrees F. To keep it under 190 F I have to suspend other projects and limit it to 5, sometimes 6 Rosetta tasks. This computer will run any combination of 17 Asteroids or Einstein tasks and still stay under 190 F. Maybe 9 WCG tasks. It will only run 1 Milky Way task, plus occasionally one Asteroids or Einstein task at a time. But Milky way tasks go very quickly, sometimes in 12 minutes or one hour at the most. I see that Rosetta now has no tasks. S. Gaber Oldsmar, FL |
|
Tom M Send message Joined: 20 Jun 17 Posts: 140 Credit: 30,602,375 RAC: 102,732
|
Steve G, There used to be a Windows up that played well with Boinc. It would throttle the cpu temperature below what you set the limit at. Maybe someone else remembers or can find it... Proud member of the O.F.A. (Old Farts Association) |
|
Grant (SSSF) Send message Joined: 28 Mar 20 Posts: 1848 Credit: 18,534,891 RAC: 0 |
Steve G,And it is bad for your CPU to run it flat out, then run it slow, then run it flat out, then run it slow, then run it flat out then run it slow (which is what that does). Thermal stress is not good for electronics. Any system from the last 10 years or so will self-throttle when it reaches it's thermal limit. Even so, keeping your CPU at 80°c or less will do wonders for it's longevity, even if it is rated to operate at as much as 105°c. The AMD Ryzen 7 5700G is rated at a max of 90W, so very low power. Even at 100% load the stock Wraith cooler correctly fitted should keep the temperature below 95°c with a reasonably well ventilated case with an ambient temperature of around 30°c, but the stock cooler is very, very basic. Fixing the problem with the CPU/system cooling would be the better option- a US $30 dual fan aftermarket cooler would be overkill, but it would keep it cool no matter what. eg the Thermalright Peerless Assassin 120 SE V3 is capable of keeping a 200W CPU at less than 60°c over ambient at 100% load for around US $33. The next best option would be to just limit the number of cores/threads being used by BOINC. Grant Darwin NT |
|
Bill Swisher Send message Joined: 10 Jun 13 Posts: 63 Credit: 53,830,766 RAC: 137,706
|
The AMD Ryzen 7 5700G is rated at a max of 90W, so very low power. Agree with this. I have 3 of them running, well 2 at the moment...1 is down in Arizona and it's powered down, apparently it was 109F there today and it's supposed to warm up a bit next week. I did use a Noctua NH-L9a-AM4 fan for them, the case has a limitation on how "tall" things can be. Right now, running 16 threads at 100% utilization, ones at 90C and the other is at 95.8C. Long ago I wrote a bash script, that ran several time per hour, to adjust the <niu_max_ncpus_pct>100.000000</niu_max_ncpus_pct> in the /var/lib/boinc/global_prefs_override.xml file to keep the temps down. Then I discovered the processor will throttle itself. So it was all a nice learning experience. :-) 
|
Message boards :
Number crunching :
Problems and Technical Issues with Rosetta@home
©2025 University of Washington
https://www.bakerlab.org