21) Message boards : Number crunching : Upload fails (Message 4325)
Posted 24 May 2020 by Falconet
Post:
https://boinc.bakerlab.org/rosetta/prefs.php?subset=project

"Target CPU Time"

The runtime is fixed. Default is 8 hours (usually ends a little before in my experience). However, if the task is working on a model that hasn't finished by the time it reaches 8 hours of CPU time (or whatever is set on the preferences), it has 4 more CPU hours to finish that model. If it doesn't, the "watchdog" software kicks in and kills the task. Which I guess explains your 7 hours (8 in prefs, I assume) up to 12 hours (the 4-hour cut-off) range across your tasks..


See my post https://boinc.bakerlab.org/rosetta/forum_thread.php?id=13644&postid=92449 and the following post from a Rosetta moderator.

The link you sent didn't work but I've seen you on the Rosetta forums so I easily found your tasks. Most of your tasks seem to respect the 8 hour target.
As to why some end earlier, I don't really know but I do remember 1 or 2 that ended below 7 hours. Maybe the Rosetta software thinks it wouldn't finish the next model in the time left till the target runtime so it just stops there?

The way I understand Rosetta is that if not for a CPU runtime target or the watchdog, the Rosetta software would go on generating structures and decoys for whatever protein input "forever".


Interesting. And cool that every project can run completely differently within the Boinc structure.

I think the best way to test Rosetta, and I'll try it tomorrow, is to set it doing some tasks in Ubuntu, wait until they get validated, then see how many points I get compared to the same amount of run time in Windows. I'll test Universe first though as that should be easiest, then LHC (if I can work out how to install Virtualbox in Ubuntu!), then Milkyway and Einstein on GPU (if I can get a Linux driver for the GPU), then I'll leave it overnight on Rosetta and check the validated results the next day.


Good luck.

Installing VirtualBox should be as easy as installing BOINC. Both are in the Ubuntu repositories.
Open the software Center, search for BOINC and VirtualBox, install. Then run.

I do not know if you need to reboot because of Virtualbox so that's something to consider when running of the USB. Anyway, try installing Virtualbox first and then BOINC and see if it works.

If you encounter issues, feel free to post here!
22) Message boards : Number crunching : Upload fails (Message 4323)
Posted 24 May 2020 by Falconet
Post:
https://boinc.bakerlab.org/rosetta/prefs.php?subset=project

"Target CPU Time"

The runtime is fixed. Default is 8 hours (usually ends a little before in my experience). However, if the task is working on a model that hasn't finished by the time it reaches 8 hours of CPU time (or whatever is set on the preferences), it has 4 more CPU hours to finish that model. If it doesn't, the "watchdog" software kicks in and kills the task. Which I guess explains your 7 hours (8 in prefs, I assume) up to 12 hours (the 4-hour cut-off) range across your tasks..


See my post https://boinc.bakerlab.org/rosetta/forum_thread.php?id=13644&postid=92449 and the following post from a Rosetta moderator.

The link you sent didn't work but I've seen you on the Rosetta forums so I easily found your tasks. Most of your tasks seem to respect the 8 hour target.
As to why some end earlier, I don't really know but I do remember 1 or 2 that ended below 7 hours. Maybe the Rosetta software thinks it wouldn't finish the next model in the time left till the target runtime so it just stops there?

The way I understand Rosetta is that if not for a CPU runtime target or the watchdog, the Rosetta software would go on generating structures and decoys for whatever protein input "forever".
23) Message boards : Number crunching : Upload fails (Message 4319)
Posted 24 May 2020 by Falconet
Post:
For example, most of my Universe@home tasks on Ubuntu 20.04 on my AMD Ryzen 5 1400 3.2 GHz take just over 1 hour to finish. On WIndows,and from memory, closer to 3 hours.


If they go three times faster, does that mean the CPUs are working 3 times harder? And generating 3 times as much heat by using 3 times the electricity? I'll use a watt meter on the wall socket when I do this to find out. If they aren't hotter, it's even stranger that they can do more work without using more power (or is Windows inserting extra pointless instructions in there?). If they are hotter, I'm going to have to buy bigger fans.



No difference in temperatures. Around 50º Celsius on both Operating systems.
I did not check with Universe@home, but with the SCC project over at WCG, which ran much faster on Linux, power usage was the about same on both Operating systems (around 83 watts).

Over at WCG, it was speculated by some members that the speedup verified with the AutoDock Vina sciences (SCC, etc) was due to better Linux memory management.

I can't comment on GPU performance under Linux, nor on LHC CPU, but Rosetta@home, considering that the runtime is fixed, we would have to run the same workunit on Windows and Linux and check the number of decoys/structures computed over the same 8/12/16/24 hours (whatever is set on your Roseta@home preferences) to see under which OS more structures/decoys were computed. So it will be hard to judge which OS is better on the Rosetta project.
24) Message boards : Number crunching : Upload fails (Message 4316)
Posted 24 May 2020 by Falconet
Post:
Ubuntu is fine. The only difference between Ubuntu flavours is RAM usage and maybe a little bit of CPU because of whatever desktop environments they use (the interface)

Xubuntu should use less RAM and maybe a little bit less of CPU too. Other than that, no difference.

You can just run it off the USB if you'd like to try it first (once you reboot, everything you install or save is reset though).


So where are programs installed? Into a RAM drive? I'd assumed the USB stick was behaving like the hard disk.

Anyway that will do. I can quickly install Boinc and attach to a single project and directly compare it to the other server still running Windows 10.



I believe it boots into the RAM so everything is lost afterwards.
Once you boot up, just find the software manager, look for BOINC and install.
25) Message boards : Number crunching : Upload fails (Message 4314)
Posted 24 May 2020 by Falconet
Post:
Ubuntu is fine. The only difference between Ubuntu flavours is RAM usage and maybe a little bit of CPU because of whatever desktop environments they use (the interface)

Xubuntu should use less RAM and maybe a little bit less of CPU too. Other than that, no difference.

You can just run it off the USB if you'd like to try it first (once you reboot, everything you install or save is reset though).
26) Message boards : Number crunching : Upload fails (Message 4312)
Posted 24 May 2020 by Falconet
Post:
You'd get much faster runtimes if you switched to Linux ;)


I find it hard to believe the OS has anything to do with processing time. Sure, maybe Windows uses 2% of the CPU and Linux 1%, but that only changes Boinc from 98% to 99%, not worth doing. Surely the Universe task is written as well as the Universe coders write it, and makes use of whatever instruction set my CPU has. The OS it's under cannot change how fast it is.



Universe@home is much faster under Linux than under Windows.
Confirmed by the project's admins. And by my observations and that of others.

See this post and thread: https://universeathome.pl/universe/forum_thread.php?id=526&postid=4183

OS does make a difference. Universe is faster on Linux than on Windows, TN-Grid is faster on Linux than on Windows, all the AutoDock VINA sciences at WCG were much much faster under Linux than Windows. Some applications just run better on Linux. Others run the same.

For example, most of my Universe@home tasks on Ubuntu 20.04 on my AMD Ryzen 5 1400 3.2 GHz take just over 1 hour to finish. On WIndows,and from memory, closer to 3 hours.

If those 2 servers are dedicated crunchers, try a Live USB of Ubuntu on one of them and see if it's worth it.
27) Message boards : Number crunching : Upload fails (Message 4308)
Posted 23 May 2020 by Falconet
Post:
Yes. We got a developer who try to make GPU app for the project, unfortunately he resign because he got struggles to port application algorithm to GPU. This is not a surprise as our application base was written since 2002 when nobody expect GPU's with compute possibilities...

This is very common problem with science app that not all algorithms can be ported to GPU.

But...

We still think about it, slowly change and clear code and maybe... But this not happens in this year definitely :(


That is a shame. But I will be adding 48 cores shortly on two xeon servers I'm building from scrap parts. If the pentathlon hasn't eaten all your tasks or melted your ethernet I'll do some more.



You'd get much faster runtimes if you switched to Linux ;)
28) Message boards : Number crunching : Cannot Upload or Download Tasks (Message 3443)
Posted 28 Mar 2019 by Falconet
Post:
I have someone who contacted me via the BOINC user help with this problem. All projects work fine except for this one.


Previous 20




Copyright © 2024 Copernicus Astronomical Centre of the Polish Academy of Sciences
Project server and website managed by Krzysztof 'krzyszp' Piszczek