Hi,

starting a few days ago (maybe with the update to rosetta 5.12, but I'm not sure about this) my system becomes extremely unresponsive while I run rosetta.

I'm doing software development on this machine and I'm running BOINC in the background while I'm doing work. This hasn't been a problem up to now, since it didn't seriously affect system performance. But starting some days ago, keyboard input is extremly unresponsive (i'm using a PS/2 keyboard; my USB mouse is working well, however). This is not the case when I'm running other BOINC applications (Seti@home, Einstein@Home, World Community Grid).

I have tried limiting the CPU usage of rosetta to 80% using Thread Master, but this doesn't solve my problem.

Some data about this machine:
Athlon XP 2500, nForce2 Chipset, 1GB RAM, Windows 2000 with all the latest update stuff from M$

Please let me know what I can do about this. I can't continue running rosetta on this machine as long as this isn't resolved.

Markus

---

They found a problem in v5.12 with some interaction with some R@H diagnostic code and BOINC APIs (you said you're doing SW development, so I feel I can talk that way :)

Bottom line, memory contention issues. Now resolved in v5.13 which you will get with your next WU download. You might just suspend the WU, download another and crunch on that... then when you leave your PC for the day, release the old 5.12 WU again so it will finish out without impairing your productivity.

In general, SW development is memory intensive. And R@H is pretty memory intensive too. But they are making great strides with reducing R@H memory requirements. So further such changes are presently being tested on the Ralph project.

---

Add this signature to your EMail:
Running Microsoft's "System Idle Process" will never help cure cancer, AIDS nor Alzheimer's. But running Rosetta@home just might!
https://boinc.bakerlab.org/rosetta/

They found a problem in v5.12 with some interaction with some R@H diagnostic code and BOINC APIs (you said you're doing SW development, so I feel I can talk that way :)

That's fine with me. :)

Bottom line, memory contention issues. Now resolved in v5.13 which you will get with your next WU download. You might just suspend the WU, download another and crunch on that... then when you leave your PC for the day, release the old 5.12 WU again so it will finish out without impairing your productivity.

I had some other work to do today, so I could finish this last WU with 5.12. 5.13 seems to work fine up to now.

In general, SW development is memory intensive. And R@H is pretty memory intensive too. But they are making great strides with reducing R@H memory requirements. So further such changes are presently being tested on the Ralph project.

Well, I don't mind if it takes 5 seconds longer to start up my IDE or to compile my code, but I can't work if I have to wait 5 seconds to see my keyboard input...
Anyway, it seems to work now. :) Thank you very much!
Markus

---