Problems with Rosetta version 5.85 (or 5.86 for linux)

Message boards : Number crunching : Problems with Rosetta version 5.85 (or 5.86 for linux)

To post messages, you must log in.

Previous · 1 . . . 5 · 6 · 7 · 8

AuthorMessage
Profile Greg_BE
Avatar

Send message
Joined: 30 May 06
Posts: 5652
Credit: 5,622,096
RAC: 71
Message 50281 - Posted: 3 Jan 2008, 10:51:33 UTC - in response to Message 50275.  
Last modified: 3 Jan 2008, 10:56:17 UTC

So... no resolution here ? 5 of my cpu's have been out of service since Dec. 20

On line but unable to get any work units that can be processed in 256 MB on 2.6 Ghz intel hyperthreading processors. Too bad.


Since BOINC sees a Hyperthreaded CPU as a two core processor and crunches two work units at a time on it you really only have 128MB of memory per CPU so it does not meet minimum memory requirements.
You could turn off Hyperthreading in the bios and run it as a single core processor or get more memory.

rochester ny 3 has only 128mb and seems to be running ok


jegs has plenty of work now after a few errors.
so whatever it was, it was just one of those Rosie errors that jams things up.
ID: 50281 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile EdMulock
Avatar

Send message
Joined: 14 Mar 06
Posts: 30
Credit: 2,347,485
RAC: 0
Message 50408 - Posted: 6 Jan 2008, 19:43:13 UTC

Status update:

Following suggestions posted here, I adjusted preferences to allow a max of one CPU. This indeed limited the scheduler to one task on hyper threaded machines. So far so good. I did encounter one anomaly when a task ( the only one running ) stalled and reported waiting for memory. I'm not sure where it thought it would get more. No limits set and system managed memory enabled. Hundreds of GB not enough ? I aborted the job an Boinc continued.
ID: 50408 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Thomas Leibold

Send message
Joined: 30 Jul 06
Posts: 55
Credit: 19,627,164
RAC: 0
Message 50412 - Posted: 6 Jan 2008, 21:10:14 UTC - in response to Message 50408.  

I did encounter one anomaly when a task ( the only one running ) stalled and reported waiting for memory. I'm not sure where it thought it would get more.


It is not about the amount of memory installed in your computer, it is about the amount of memory available to run the client. Depending on what other applications are currently running the amount of memory available to Boinc and project clients can indeed change.

Unfortunately the Rosetta client (at least on Linux, since that is all I'm using) still has problems with Boinc task switching which requires to keep the client in memory even if it is not active (this is an option in your Boinc preferences). Keeping the inactive (waiting to run) tasks in memory however reduces the amount of memory available to other Boinc tasks. This usually only affects users who participate in multiple Boinc projects since the Boinc client will not normally switch between tasks for the same project (exception is if a non-active workunit nears the project deadline).

Team Helix
ID: 50412 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile EdMulock
Avatar

Send message
Joined: 14 Mar 06
Posts: 30
Credit: 2,347,485
RAC: 0
Message 50460 - Posted: 8 Jan 2008, 16:22:19 UTC - in response to Message 50412.  

I did encounter one anomaly when a task ( the only one running ) stalled and reported waiting for memory. I'm not sure where it thought it would get more.


It is not about the amount of memory installed in your computer, it is about the amount of memory available to run the client. Depending on what other applications are currently running the amount of memory available to Boinc and project clients can indeed change.



These machines are XP-Pro with nothing active but Boinc and running Rosetta exclusively. So all the memory was availabe to the Boinc client. Anyway, this "fix" seems to be working after two or three days of experience. Fingers crossed. BTW, Hi Thomas from a fellow Team Helix member. It has been rather frustrating to watch my RAC drop like a rock due to this problem. Either they changed Rosetta, or we found a workaround.
ID: 50460 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Previous · 1 . . . 5 · 6 · 7 · 8

Message boards : Number crunching : Problems with Rosetta version 5.85 (or 5.86 for linux)



©2022 University of Washington
https://www.bakerlab.org