Posts by genes

41) Message boards : Number crunching : Resource share: RALPH instead of Rosetta@home? (Message 172)
Posted 18 Feb 2006 by genes
Post:

And btw, as far as I can tell, there is no way to change the "leave app in memory" per project or per PC or per location (home/work/school).


"Leave in Memory" setting is under *General* preferences, not Ralph@Home preferences. You can set up different sets of preferences for Work, Home, School, ---. I set up "School" to have NO for Leave in Memory, and have 1 machine set to School. You should not run Rosetta on that machine, since it will error out. Other Boinc projects seem to be able to handle it, though. I have CPDN, Einstein, Seti, and Seti Beta on that machine, happily co-existing.

[edit]The [Work, Home, School, ---] settings apply to the entire machine, so all projects on that machine will run with those settings. Other machines can be set to different places, and will use different settings. If you only have one machine running BOINC, it really doesn't matter which location you use, just use the default. But you cannot then separate general preferences. They propagate to all projects. [/edit]

[edit]
I read this section more carefully, so I'll try to help clear up the misunderstanding:


So, it seems to me at first glance, that the ONLY way to test RALPH for the "Leave in mem" issue, without killing Rosetta's WUs, would be to test RALPH on a PCs that only run RALPH (not R@H) and any projects unaffected by this setting,


This is true.

but which don't share Rosetta on other PCs (so I can set RALPH settings to "Leave app in mem" to "No", but this setting won't "propagate" to the R@H production PCs).


This is not true. Set other non-Ralph PC's to a different location and the other projects will run according to that location. It goes by machine. You can even run Ralph on those, but you won't be testing the "leave in Memory" setting. You can test the run time there.
[/edit]

Enjoy.
42) Message boards : Current tests : Switching between projects with applications removed from memory (Message 170)
Posted 18 Feb 2006 by genes
Post:

For the purposes of the ALPHA testing, you should expect to loose processing time. That is just the nature of testing. If loss of processing time is important to you please consider if the test project is the best use of your system.


Yes, I agree. I expect to lose Ralph WU's, but I didn't want to ruin Rosetta WU's, so I am not allowing that machine to get any more Rosetta for the duration of the test. I now have a new Ralph WU on that machine, but with a 4.84 app version. What's new in 4.84?
43) Message boards : RALPH@home bug list : Report \"failure when switching projects without keeping applications in memory\" bugs here (Message 113)
Posted 17 Feb 2006 by genes
Post:
Oops -- I should have put this here, but instead I put it in the "current tests" area. Well, here it is anyway.

OK, the machine I had set "leave in memory" to OFF had an error on its one WU that it got:

http://ralph.bakerlab.org/result.php?resultid=1666

It's not getting any more at the moment (no work from project). It also just had a Rosetta WU error out. I set Rosetta to NNW on that machine for now so I won't lose any more work.

This is the machine BTW:

http://ralph.bakerlab.org/show_host_detail.php?hostid=76

44) Message boards : Current tests : Switching between projects with applications removed from memory (Message 108)
Posted 17 Feb 2006 by genes
Post:
OK, the machine I had set "leave in memory" to OFF had an error on its one WU that it got:

http://ralph.bakerlab.org/result.php?resultid=1666

It's not getting any more at the moment (no work from project). It also just had a Rosetta WU error out. I set Rosetta to NNW on that machine for now so I won't lose any more work.

This is the machine BTW:

http://ralph.bakerlab.org/show_host_detail.php?hostid=76
45) Message boards : Current tests : Switching between projects with applications removed from memory (Message 38)
Posted 16 Feb 2006 by genes
Post:
I'm having a problem with this, but not the one you're trying to fix. BOINC simply does not have enough "venues" to set up custom situations to either test specific things or to tune resources for specific machines. And since it doesn't allow "local control", we have to balance carefully.

OK, so "school" is going to have "leave in memory" OFF, all others will have it ON. Otherwise, "school" will be like "home". Good thing I can use the same resource shares for these two. Then, of course, I have to visit all the projects and update on all their web sites, or stuff will be hopelessly confused.


Previous 20



©2024 University of Washington
http://www.bakerlab.org