Maybe the PTB should update the Rosetta system requirements page?
Microsoft Windows
Windows XP 500MHz or higher 200MB 256MB
Windows 2003 Server 500MHz or higher 200MB 256MB
Windows 2000 500MHz or higher 200MB 256MB

The computer I was running Rosetta on has 512mb of memory, yet it gets messages saying 0 work downloaded due to lack of memory. Or it gets work, then BOINC manager shows it as "waiting for memory". This machine will run SETI, Einstein and ABC with no problems. If you're going to change requirements, how about the courtesy of an email notification so we can just move on to other projects instead of wasting time reading countless pages of forum posts hoping for an answer as to why nothing works right?

Outta here....

Maybe the PTB should update the Rosetta system requirements page?
Microsoft Windows
Windows XP 500MHz or higher 200MB 256MB
Windows 2003 Server 500MHz or higher 200MB 256MB
Windows 2000 500MHz or higher 200MB 256MB

The computer I was running Rosetta on has 512mb of memory, yet it gets messages saying 0 work downloaded due to lack of memory. Or it gets work, then BOINC manager shows it as "waiting for memory". This machine will run SETI, Einstein and ABC with no problems. If you're going to change requirements, how about the courtesy of an email notification so we can just move on to other projects instead of wasting time reading countless pages of forum posts hoping for an answer as to why nothing works right?

Outta here....

well there are difficult WU's with the flag high memory only, i thaught that is 1024 and up.. but there ar also WU's for 512, i dont think there are much for 256. but who knows...

I woke this morning to see this in my message tab:

"message from server: Your computer has 688MB of memory, and 763 is needed"

??????? I've done 100's of them with this AMD64 2800 since Nov 26, and haven't seen this message yet. I'm only attached to Rosetta. Any Ideas??? Thought the min was 256? It was running linux 64b at the time. It had run out of work and was sitting empty. Switched to Windows for the moment.

I woke this morning to see this in my message tab:

"message from server: Your computer has 688MB of memory, and 763 is needed"

??????? I've done 100's of them with this AMD64 2800 since Nov 26, and haven't seen this message yet. I'm only attached to Rosetta. Any Ideas??? Thought the min was 256? It was running linux 64b at the time. It had run out of work and was sitting empty. Switched to Windows for the moment.

it's task dependent - it should pick up some small memory ones if any are available but I don't think the scheduling system is intelligent enough to work this out and has to wait until smaller-memory tasks are assigned by pot luck - i think it would need a client side change to BOINC rather than a server side change...

---

it's task dependent - it should pick up some small memory ones if any are available but I don't think the scheduling system is intelligent enough to work this out and has to wait until smaller-memory tasks are assigned by pot luck - i think it would need a client side change to BOINC rather than a server side change...

So, these are my choices?

1) run another project on that machine

2) I still have 6 wus on windows, so I could raise the cpu run time from 1 hour to 24 and still have a weeks worth, but that would mean most the work on my other machines/OSes would run past deadlines. Not to mention it would completely defeat my data collection plan currently in place. So, It's looking like "option 1". But, Option one, defeats my RAC curve study (wasting the last 28 days efforts).

love these choices.

look at rochester ny 3 that computer only has 128mb

Here's what I'm trying. Set cpu run time to 24 hours. Update rosetta on that machine. Confirm successful contact with server. Set host to "network activity suspended". Change run time pref back on the website. Hopefully, they'll find some "normal" (whatever that is) size wus for us to use.

my cpu run time is 24 hrs and its a small machine rochester ny 3 has a run time of 24 hours too with only 128mb been working ok so far

the real problem is, that you have enaugh memory installed, but it cant use enaugh. so your linux is taking up to much memory, maybe you can edit the linux settings so it uses minimum memory.

the real problem is, that you have enaugh memory installed, but it cant use enaugh. so your linux is taking up to much memory,

No, it's a BOINC preference that determines how much of the memory is to be considered available to BOINC. If you edit your BOINC preferences, you can specify what percent of memory to use when the system is busy and what percent to use when the system is idle. Setting both to 100 percent will reduce memory problems with BOINC when using Linux. Note that WUs usually use far less memory under Linux than what they specify as being needed.

The project was just down for a little bit. Am I correct to presume you are now able to get work on machines that were having problems getting work previously?

---

Rosetta Moderator: Mod.Sense

Still having trouble getting work here, getting the same message relating to having insufficient memory.

---

Still having trouble getting work here, getting the same message relating to having insufficient memory.

Same here. All of my Mac OS boxes are asking for more memory and no work being accomplished. I'm shutting 9/10's of the farm down today since I'm leaving for a few months. Hope RH gets the kinks out before I get back.

---

Still having trouble getting work here, getting the same message relating to having insufficient memory.

Same here. All of my Mac OS boxes are asking for more memory and no work being accomplished. I'm shutting 9/10's of the farm down today since I'm leaving for a few months. Hope RH gets the kinks out before I get back.

thats very odd, my pc 512 box got new work about 4 hours ago and everything is back to normal now, so there should be something out there for low memory boxes of any kind now.

---

All my machines have work now. (They're mostly 512MB single core.)

I have a question, why are high memory tasks being sent to hosts

that can't do them. I have myself recived a number of reruns after

they have failed, it's not a problem for me but i thought the servers

wouldn't send them in the first place, it seems like a waste of time

and bandwidth, like this one.

https://boinc.bakerlab.org/rosetta/workunit.php?wuid=117442679

pete.

---

I'm sorry I can't help you with your question. But I have made a direct link to the task in your question
_________________________
Speedy

I have a question, why are high memory tasks being sent to hosts

that can't do them. I have myself recived a number of reruns after

they have failed, it's not a problem for me but i thought the servers

wouldn't send them in the first place, it seems like a waste of time

and bandwidth.

like this one

pete.

I'm sorry I can't help you with your question. But I have made a direct link to the task in your question
_________________________
Speedy

I have a question, why are high memory tasks being sent to hosts

that can't do them. I have myself recived a number of reruns after

they have failed, it's not a problem for me but i thought the servers

wouldn't send them in the first place, it seems like a waste of time

and bandwidth like this one.

pete.

I have a question, why are high memory tasks being sent to hosts

that can't do them. I have myself recived a number of reruns after

they have failed, it's not a problem for me but i thought the servers

wouldn't send them in the first place, it seems like a waste of time

and bandwidth, like this one.

https://boinc.bakerlab.org/rosetta/workunit.php?wuid=117442679

pete.

well you have 1024 mb of memory installed, so it will send task that use up to 1024 mb, but then there has to run an OS and BOINC so you cant use all the memory you have, so you might miss a bitt of memory that way.

Each specific task can be resent as many as 3 times. Normally the first person it is sent to completes it and returns it within the deadline, and so it is not sent again. If the first person fails for any reason, including the deadline, then it is resent. Often you will see that the second person that gets the task completes it normally. In addition to a completed result, this also gives the Project Team information about whether specific operating systems are having problems that are not seen on others. So, they are often resent, but only to a very limited degree.

---

Rosetta Moderator: Mod.Sense