Something different to slow performance, has anyone else had the problem of very short completion times for Ralph 5.12 workunits?
I just received 19 WU's (I have a 2 day cache) and the system has given me only 4 days (till 13th May) to complete them. I am using a dual AMD 848 machine and have suspended work for Einstein and Rosetta on this machine so that Ralph will have enough time to complete all the workunits. They were stamped with completion times of 4 hours 58 minutes each though this has now reduced to 4 hours 34 minutes each. this means I will get through about 4 to 5 per day per cpu.

---

Here's one I see tonite. I have no background on this one:

I experienced problem with resizing in windowed screensaver mode, still running 5.10... Is it fixed in 5.12? And a suggestion: would be nice to see what the lowest found RMSD/Energy was over each model!

---

The following 4 pics are of the same wu. I'm only moving the right hand side of the Ralph box and clicking another picture. At some point the bottom scrolls off the screen.

Great, these posts on graphics have been useful. We'll probably have to limit our WU descriptions to one line so that the rest of the text doesn't get pushed off the screen for some clients.

Here's one I see tonite. I have no background on this one:

---

This is anecdotal only, but having seen Son Goku's post I will chip in that I too have seen my system get noticeably sluggish when Ralph is loaded,
only since about 5.11 or 5.12. I've been running BOINC over a year with the same hardware (P4, HT restricted to one pseudo-cpu, 1GB memory)
and this hasn't happened before, and there are other projects I run like WCGrid's FightAids@Home which use more memory (virtual and not)
which don't cause this. I don't understand the reason, unless Task Mgr lies about memory and VM sizes (quite possible)...
but I've had things happen like my specific applications consistently failing or small applications taking huge amounts of time to start up,
only once I have let Ralph run. Even if Ralph is not currently running, as long as it has run and is still in memory.

I know this sounds a bit nuts but I've watched it several times by going through the sequence from boot up with all boinc projects suspended,
enabling different combinations of projects -- including combinations which add up to more memory usage -- and watching things flake out
as soon as Ralph has loaded and only when Ralph is loaded, with no other evidence of problems with the box.

Out of time to pursue it more, and I'll probably NNW Ralph for a while as I need this machine to function properly, and this problem seems like
a Twilight Zone ep. If more than one or two of us are affected I'm happy to pursue it further when I get some time.

p.s. I do use the screen saver, going to blank screen after 5 minutes. Occasionally I'll run the graphics manually but not often. Single-user install.

---

Well, I do think a 1 liner is cutting things a little too tight for WU description, however there does come a point where large gfx can mount up...

BTW, just having the window not maximized, and then doing an (alt + print screen), will just copy the current app window to the clipboard, rather then the whole desktop. This would cut the start menu, and other such Windows items outa the screen capture...

---

Hello, in this screen i can't see the text in its entirety.

TEST_HOMOLOG_ABRELAX_hom008_1fna__503_3_0 using rosetta_beta version 512
And i see problems with Accepted Energy and RMSD.
Sorry for my bad english

---